Version 15 (Eric Raymond, 04/11/2011 01:08 pm)
We've written an [[Introduction]] to bufferbloat problem that we believe is both accessible to non-technical readers and informative to techies. We recommend you start there to get a feel for the nature and scope of the problem. Then, read our [[Mission|mission statement]] to find out what we're doing about it.
There's also a [[Glossary]] that goes into more technical depth on bufferbloat-related terminology. You may find an older [[TechnicalIntro|technical introduction]] interesting if you are a programmer or network engineer.
Many of the [[CongestionSymptoms|symptoms]] of bufferbloat-induced congestion have an immediate, user-visible impact on performance. If you're not sure you are seeing these, there are [[Experiments|experiments]] you can perform on your home hardware to detect bufferbloat problems. If you want to jump straight to fixing the problem, we have a [[Mitigations_and_Solutions|Mitigation and Solutions]] page.
Much of the original analysis and discussion of bufferbloat took place on technical blogs. We have collected a [[Good_blog_discussions|tasty selection of blog references]] for your reading pleasure.
You can read bufferbloat-related [[Quotes]] from the great, near-great, and and not-so-great. A page of unashamedly geeky [[Humor]] exists as well.
Our project has very active "mailing lists":https://lists.bufferbloat.net on which we're developing anti-bufferbloatr fixes, diagnostic tools, documentation, and other fun things. You cam also look at a [[ToDo]] list of projects that need work.
Please "join the project":http://www.bufferbloat.net/account/register and pitch in.