SBJ95
07-27-2007, 01:24 AM
DISCLAIMER: Some of the things done in here are disliked by some site and/or server admins, so do not blame me if you get kicked from a website.
DISCLAIMER, DISCLAIMER: Messing around in here COULD make your Firefox not work, so if that happens, either due to a bad change on my part, or a mess-up on your part, do not blame me.
Note: If one of these isn't there, right-click, say new, and say integer if it's a number, string if it's words, or boolean if it's true/false.
Want to learn how to optimize Firefox? This is your guide. Note that some changes made in here will not make a difference, it depends on your scenario.
To start out, open a new tab and type about:config in the address bar. It'll bring up a page with a bunch of (more or less) nonsense. First type in browser.tabs.tabMinWidth in the search bar, and wait for that line to come up. What this is, is it controls how small (in pixels of width) tabs can get. This is mostly personal preference. Mine is set at 20. (Note, to change the value, just double-click on the far-right value and change it in the box.
Next, search for network.http. Several lines will come up. The first one, max connections is set for me at 32, but again, it's personal preference. All of these involve multiple connections to a server, or sending multiple requests at a time. pipelining is the latter, multiple connections is the former. For me, max connections per server is set to half of max connections, but again, it's personal preference. The next two, max persistent connections, should be set the same, I set mine at half of max connections per server; the max persistent connections per proxy only applies if you use a proxy server, however, so if you don't, then leave it alone. Next, set the next three boolean (true/false) values to true. However, the latter two only apply with proxies, so follow my advice above. Set network.http.pipelining.maxrequests to however high you feel comfortable with, mine is set at 8. Last in that grouping is network.http.request.max-start-delay, which controls how long it starts to process webpage info. I think. I'd set it to zero.
That's all for now. I swear I knew of more, but if I figure out more, I'll be sure to update the guide. Hope this helps.
Oh, and if you tried this out, post and let me know how it worked.
DISCLAIMER, DISCLAIMER: Messing around in here COULD make your Firefox not work, so if that happens, either due to a bad change on my part, or a mess-up on your part, do not blame me.
Note: If one of these isn't there, right-click, say new, and say integer if it's a number, string if it's words, or boolean if it's true/false.
Want to learn how to optimize Firefox? This is your guide. Note that some changes made in here will not make a difference, it depends on your scenario.
To start out, open a new tab and type about:config in the address bar. It'll bring up a page with a bunch of (more or less) nonsense. First type in browser.tabs.tabMinWidth in the search bar, and wait for that line to come up. What this is, is it controls how small (in pixels of width) tabs can get. This is mostly personal preference. Mine is set at 20. (Note, to change the value, just double-click on the far-right value and change it in the box.
Next, search for network.http. Several lines will come up. The first one, max connections is set for me at 32, but again, it's personal preference. All of these involve multiple connections to a server, or sending multiple requests at a time. pipelining is the latter, multiple connections is the former. For me, max connections per server is set to half of max connections, but again, it's personal preference. The next two, max persistent connections, should be set the same, I set mine at half of max connections per server; the max persistent connections per proxy only applies if you use a proxy server, however, so if you don't, then leave it alone. Next, set the next three boolean (true/false) values to true. However, the latter two only apply with proxies, so follow my advice above. Set network.http.pipelining.maxrequests to however high you feel comfortable with, mine is set at 8. Last in that grouping is network.http.request.max-start-delay, which controls how long it starts to process webpage info. I think. I'd set it to zero.
That's all for now. I swear I knew of more, but if I figure out more, I'll be sure to update the guide. Hope this helps.
Oh, and if you tried this out, post and let me know how it worked.