Skip to content
shredstream.sh
Get a connection
All tools
Tool

Calculate shred-feed bandwidth

Turn a measured datagram rate and mean size into bits per second, packets per month, and 30-day storage with every unit shown.

Over what period

Sustained rate

48.0 Mbps

5.72 MiB/s payload

Decimal megabits, which is how transit is sold and how an interface counter reports.

Volume over 30 days
15.55 TB
14.14 TiB binary. Providers bill the first, disks report the second.
Packets over 30 days
12,960,000,000
Worth knowing if anything in your path charges or limits per packet.

These are payload bytes unless you add overhead. Solana's traffic is not constant: it moves with network activity, and a busy period runs meaningfully above the mean. Size links and budgets against the peak you are willing to survive, not the average you were quoted.

2 inputs calculate bandwidth and storage

The bandwidth calculator starts from arrival frequency and average datagram length. Its output covers payload bytes each second, decimal Mbps, binary MiB/s, period packet count, decimal TB, binary TiB, and optional link-layer overhead.

Default values provide an initial busy-feed scenario. Replace them with observed arrival frequency and average size before planning receiver capacity.

Method

Denote packets each second by p, average bytes per packet by s, and period days by d.

text

bytes_per_second = p * sbits_per_second = bytes_per_second * 8Mbps = bits_per_second / 1,000,000 seconds = d * 86,400period_packets = p * secondsperiod_bytes = bytes_per_second * secondsTB = period_bytes / 1,000,000,000,000TiB = period_bytes / 1,099,511,627,776

Network Mbps uses decimal units. Storage TB also uses decimal units. TiB uses powers of two. The tool displays both labels and never calls them interchangeable.

Optional overhead is a scenario, not part of the payload calculation:

text

wire_Mbps = p * (s + overhead_bytes_per_packet) * 8 / 1,000,000

The user selects IPv4 or IPv6 assumptions, VLAN tags, and tunnel bytes. The component lists every included header rather than supplying an unexplained percentage.

Calculate a 30-day traffic projection

Model a 4,800-packet arrival rate with 1,175 payload bytes on average over 30 days.

text

bytes_per_second = 4,800 * 1,175                 = 5,640,000 bits_per_second = 5,640,000 * 8                = 45,120,000 Mbps = 45,120,000 / 1,000,000     = 45.12

The selected 30-day interval spans 2,592,000 seconds.

text

period_packets = 4,800 * 2,592,000               = 12,441,600,000 period_bytes = 5,640,000 * 2,592,000             = 14,618,880,000,000 TB = 14.61888   = 14.6 rounded to one decimal place TiB = about 13.30

The arithmetic shows how the supplied inputs determine every result. It also exposes the unrounded byte total for cloud billing and disk plans.

Add wire overhead carefully

Treat the supplied 1,175-byte average as UDP-layer payload above standard IPv4 Ethernet. One planning model adds 20 IPv4 bytes, 8 UDP bytes, 14 Ethernet header bytes, 4 frame-check bytes, 8 preamble bytes, and 12 inter-frame-gap bytes. The result is 66 extra wire-time bytes for each datagram.

text

wire_bytes_per_packet = 1,175 + 66 = 1,241wire_Mbps = 4,800 * 1,241 * 8 / 1,000,000          = 47.6544 Mbps

This is an estimate at a named layer. Packet captures, interface counters, and provider bills may count different bytes. IPv6, VLANs, VPNs, and tunnels change the result.

Packet rate and byte rate size different systems

In this scenario, 45.12 Mbps occupies a small fraction of a 1 Gbps link. The 4,800 packet-per-second input still drives receive calls, descriptors, interrupts, timestamps, queue entries, allocations, and decoder iterations.

One per-packet action repeats 12.4416 billion times over 30 days. A 32-byte metadata record for each arrival adds about 398.1312 GB decimal before database overhead. A log line can be larger.

Use byte rate for link, storage, and transfer billing. Use packet rate for CPU, queue, interrupt, and metadata planning. Use short-window observed peaks for both.

Convert rate into a cost input

This projection can pass 14.61888 TB into the self-hosting or price comparator tools. Keep the full value for arithmetic and round only for display. Under the supplied payload assumption, a provider using decimal GB should receive 14,618.88 GB.

Cloud architecture can charge the same bytes more than once through a load balancer, cross-zone hop, packet mirror, object-store write, or replica. Draw each hop and apply its own rate. Incoming internet traffic being free does not make every downstream hop free.

Limitations

The starting values illustrate one busy stream. They are not measurements, protocol maxima, future guarantees, or burst percentiles. Feed behavior changes with network load and protocol changes, so replace them with your own observations.

The monthly projection assumes a constant mean for every second of the selected period. Outages reduce received bytes. Higher future load increases them. Storage adds capture framing, timestamps, checksums, filesystem overhead, indexes, and replicas.

The overhead model depends on observation layer. Generic packet capture can omit physical framing. NIC offload behavior can change counters visible to the host. Cloud meters use provider definitions.

Validate the projection

Count accepted source datagrams and payload bytes over a fixed interval on the receiver. Divide bytes by elapsed seconds and packets by elapsed seconds, then compare those values with interface and application counters. Repeat over 10-millisecond, 100-millisecond, one-second, and longer windows where the instrumentation can keep up.

Keep mean, p95, p99, and maximum window rates. The monthly projection uses the long-window mean, while link, queue, and CPU headroom follow short-interval distributions. Document measurement date and packet layer so another operator can reproduce the conversion.

The calculator sizes quantities, not delivery quality. A link with enough mean capacity can still drop microbursts or face packet-per-second limits. Validate with short-window counters and production-like traffic.

How it works out the answer

Compute bytes_per_second = packets_per_second × mean_packet_bytes, bits_per_second = bytes_per_second × 8, and period_bytes = bytes_per_second × days × 86,400. Report Mbps and TB with decimal divisors, MiB/s and TiB with binary divisors, and optional wire overhead as packets_per_second × overhead_bytes × 8.

Questions

How does packet rate become Mbps?
Arrival frequency multiplied by average packet bytes yields bytes each second. Multiply that result by eight, then divide by one million for decimal Mbps. The calculator keeps supplied inputs and its unrounded result visible.
Why does the calculator show both TB and TiB?
TB uses decimal trillions of bytes, while TiB uses powers of two. The example monthly total is 14.61888 TB or about 13.30 TiB. Network and cloud billing commonly use decimal units, while operating-system storage tools may show binary values. Both labels prevent false disagreement.
Does the projected storage include packet-capture and filesystem overhead?
No. The projection follows the arrival frequency and average payload entered by the user. Capture record headers, timestamps, checksums, file allocation, indexes, replicas, and optional network headers add capacity. The tool can model named network overhead, while storage overhead remains a separate planning input.