52 points

Just look at the bit rate of what you are streaming and multiply it by 3 then add a little extra for overhead.

permalink
report
reply
1 point
*

I don’t have a jellyfin server but 1MB/s (8mbps) for each person watching 1080p (3.6Gb per hour of content for each file) seems reasonable. ~3MB/s (24mbps) upload and as much download should work.

permalink
report
reply
14 points

1mbps is awfully low for 1080. Or did you mean megabyte rather than megabit?

permalink
report
parent
reply
4 points
*

I had a hunch that writing the actual Upload/download speed tather than mbps was probably wrong. My bad, my internet provider lingo is rusted.

permalink
report
parent
reply
3 points

Gotcha. Typically lowercase b=bit and uppercase B=Byte, but it’s hard to tell what people mean sometimes, especially in casual posts.

Come to think of it, I messed up the capitalization too. Should be a capital M for mega.

permalink
report
parent
reply
2 points

Why don’t people use Mb/s and MB/s which makes it so much clearer what you’re talking about

permalink
report
parent
reply
7 points
*

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

permalink
report
parent
reply
1 point

but why?

permalink
report
parent
reply
1 point
*

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

permalink
report
parent
reply
3 points

The best format imo is MB/s and Mbit/s

It avoids all confusion.

permalink
report
parent
reply
6 points

I have 35mbps upload from the ISP, and limit each stream to 8mbps. This covers direct streaming all my 1080p content and a 4K transcode as needed.

permalink
report
reply
2 points

How expensive is internet? If its cheap go overkill and don’t worry about it.

permalink
report
reply
5 points

Are you transcoding?

4mbit per client for 1080 is generally a workable minimum for the average casual watcher if you have H265 compatible clients (and a decent encoder, like a modern intel CPU for example), 6 - 8mbit per client if its H264 only.

Remember that the bitrate to quality curve for live transcoding isn’t as good as a slow, non-real-time encode done the brute force way on a CPU. so if you have a few videos that look great at 4mbit, dont assume your own transcodes will look quite that nice, you’re using a GPU to get it done as quickly as possible, with acceptable quality, not as slowly and carefully as possible for the best compression.

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 5K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments