Firefox

[TheRoper]

Also, as was briefly mentioned before, Firefox is GREAT for web developers. The web developer toolbar, and firebug extensions are a freaking awesome life saver. And another one that wasn't mentioned, IE Tab. It lets you render a page using the IE engine, either in the same tab, a new one, or a new window. It's great cuz you can open your site in a FF tab and right next to it in a IE tab to compare.

 

Plus, you don't have to actually open up the other program that way.

 

Extensions FTW.

 

 

 

edit: Also the fact that I can view an image, copy an image, or copy the URL of an image with just right-click, which would take like 2-3 using IE. And session-restore in case you accidentally close it, or computer crashes or whatever. And many more...

Edited September 18, 2007 by TheRoper

[Saggy]

I believe there's a FireFox extension called FasterFox that tunes the about:conf (or whatever it, I tend to forget these things). Anyway, someone told me that it really puts a strain on servers. In fact, I could almost swear that I remember when it was mentioned here, the server had a little downtime right afterward; those were turbulent days, though.

 

</random thought time>

[TheRoper]

^Yeah, I remember that. I don't know much about server communication, but changing "http.maxrequest" to 30 does sound like it's doing something resource intensive.

 

And yeah, when that topic was posted in Gen. Chat, everyone did it, then GTAF was all laggy. But you're right, that was during the 500 error phase, so who knows..? I'd like to find out more about it though...

[Picolini]

Thats the thing I was talking about, increasing the pipeline or whatever.

 

I found it didn't really change much at all, everything was still slow. With Firetune, it was easily 2x faster at loading pages.

[SWEETSAPRIK]

 

Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

Keep the "network.http.max-connections-per-server" bit low or you'll be assaulting every server you hit. Not to mention that setting "network.http.pipelining.maxrequests" to anything higher than 8 is useless as it doesn't do anything.

Edited September 19, 2007 by Sweets

[TheRoper]

Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

Keep the "network.http.max-connections-per-server" bit low or you'll be assaulting every server you hit. Not to mention that setting "network.http.pipelining.maxrequests" to anything higher than 8 is useless as it doesn't do anything.

What is considered 'low' for that one? Mine's at 16.

And my pipelining.maxrequests is set to 4 (and it says that's the default)

 

Here's the deal: I've made some manual tweaks (don't remember which ones) before running firetune. Now, I kinda wish I hadn't since I don't know which ones are worth it. Is there any way to reset them all to defaults so then I can run firetune again and be sure I got the best settings..?

 

Thanks.

[SWEETSAPRIK]

For "network.http.max-connections-per-server" 8 is the default. The only real options are 1-255. What number is too high really depends on the server you're hitting. For example, 16 probably won't have any ill effects on big site like CNN or Google or something, but too many people doing it on smaller sites like GTAF will. 16 shouldn't really be that bad though, you're effectively two people browsing with default settings, though I can't really speak for the people who run the sites you hit.

 

Also, it won't really matter what you set it to if the "network.http.max-connections" is set lower. The default on that is 24. If you set the first to 25 but left this at 24 you could never make that 25th connection to a single server because you wouldn't be allowed to make more than 24 connections to any servers at any one time.

 

But the options for "network.http.pipelining.maxrequests" are only 1-8. I have no idea what the effect of other settings are, but I would assume anything higher than 8 counts as 8.