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.
- S on A 2024 Freedom Agenda (ver. 0.1)
- C.E. Petit on Does Tripit Think I’m on a Watch List or Financial Sanctions List?
- jal on Does Tripit Think I’m on a Watch List or Financial Sanctions List?
- C.E. Petit on He’s Wrinkled, Rested, and Ready
- Michael Froomkin on Vote Castro in the April 25 Coral Gables Runoff (Can You Say that in Miami?)
Subscribe to Blog via EmailJoin 2,772 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.