45
you are viewing a single comment's thread
view the rest of the comments
[-] SigHunter@lemmy.kde.social 7 points 6 months ago* (last edited 6 months ago)

Back in the day, the rule was mbit (megabit) for data in transfer (network speed) and MB (megabyte) for data at rest, like on HDDs

[-] dysprosium@lemmy.dbzer0.com 1 points 6 months ago* (last edited 6 months ago)

So mbit/s instead of Mbit/s ? But the M in Mega is always capitalized though, except the k in kilo.

[-] Moneo@lemmy.world 1 points 6 months ago
[-] realbadat@programming.dev 2 points 6 months ago

Bigger number sounds better for the ISP.

[-] rhys@mastodon.rhys.wtf 1 points 6 months ago

@Moneo @SigHunter Networking came to be when there were lots of different implementations of a 'byte'. The PDP-10 was prevalent at the time the internet was being developed for example, which supported variable byte lengths of up to 36-bits per byte.

Network protocols had to support every device regardless of its byte size, so protocol specifications settled on bits as the lowest common unit size, while referring to 8-bit fields as 'octets' before 8-bit became the de facto standard byte length.

[-] bitwaba@lemmy.world 1 points 6 months ago

The real answer?

Data is transmitted in packets. Each packet has a packet header, and a packet payload. The total data transmitted is the header + payload.

If you're transmitting smaller packet sizes, it means your header is a larger percentage of the total packet size.

Measuring in megabits is the ISP telling you "look, your connection is good for X amount of data. How you choose to use that data is up to you. If you want more of it going to your packet headers instead of your payload, fine." A bit is a bit is a bit to your ISP.

this post was submitted on 20 May 2024
45 points (95.9% liked)

Selfhosted

40383 readers
379 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS