Firefox on steroids. Nothing the advanced user will not have done already, but a very nice step-by-step guide for the rest of the world.
A Personal Blog
by Michael Froomkin
Laurie Silvers & Mitchell Rubenstein Distinguished Professor of Law
University of Miami School of Law
My Publications | e-mail
All opinions on this blog are those of the author(s) and not their employer(s) unelss otherwise specified.
Who Reads Discourse.net?
Readers describe themselves.
Please join in.Reader Map
Recent Comments
- Jennifer Cummings on Are Coral Gables Police Cooperating with ICE?
- Wendy M. Grossman on John Lithgow Reads Timothy Synder’s 20 Lessons On Tyrrany
- Michael on No Joke
- Wendy M. Grossman on No Joke
- Brooks Fudenberg on I Voted
Subscribe to Blog via Email
Join 51 other subscribers
Their example of 30 for the number of max requests on pipelining is probably too high to do any good and it can be kind of mean to webservers. Also, although changing the paint delay can make it appear somewhat faster, it will probably slow down the total time to render a page, since it will have to do more total drawing. But, if you like it better that way, that’s fine too.
Under 30, what’s a good number, from the webserver side?
Mozilla itself seems to suggest 8. I’ve also seen comments that with 4 or 5 you get most of the benefits. The default setting with my version of Firefox is 4. It also appears that some websites don’t always load properly if you use pipelining. So although it makes it faster in a lot of cases, you have to beaware it can fail to work sometimes.