Selfhosted

59973 readers

422 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

144

Increase your Linux Server Internet Speed with TCP BBR Congestion-Control (www.cyberciti.biz)

submitted 2 years ago by HumanPerson@sh.itjust.works to c/selfhosted@lemmy.world

26 comments fedilink hide all child comments

I recently found this on Reddit while looking into why jellyfin is effected so much by latency. I found that this worked and thought I would share it because it is generally applicable, takes five minutes to setup, and helps a lot with bandwidth on higher latency connections. I admit I am not sure of the technical stuff behind this, so if anyone would like to chime in that would be much appreciated.

you are viewing a single comment's thread
view the rest of the comments

[–] christophski@feddit.uk 7 points 2 years ago (2 children)

Are there any downsides to this? Why isn't it default if it is so drastically better?

[–] far_university1990@feddit.de 6 points 2 years ago* (last edited 2 years ago)

https://en.wikipedia.org/wiki/TCP_congestion_control#TCP_BBR

List some issues, but only earlier version, not BBR3

BBR1:

researchers like Geoff Huston and Hock, Bless and Zitterbart found it unfair to other streams and not scalable.

Hock et al. also found "some severe inherent issues such as increased queuing delays, unfairness, and massive packet loss" in the BBR implementation of Linux 4.9.

Soheil Abbasloo et al. (authors of C2TCP) show that BBRv1 doesn't perform well in dynamic environments such as cellular networks.

[–] HumanPerson@sh.itjust.works 3 points 2 years ago

I believe it will result in like 10% additional overhead, which may be bad on metered connections, but I am not aware of any situation that results in decreased performance. I don't really know much about this so if anyone would like to correct me, please do.