"Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once"
It's like raping the servers dude..FF2 is cap to 8 at max.
Imagine a door way big enough for 8 persons is force to 30 people at once..that will chocked the servers if everyone does that..
Heres a good tool for running FF...just extract it to a program directory and have it running on windows start.
It lowers Firefox memory usage..
Does not support Vista though.
http://firefox-ultimate-optimizer.en.softonic.com/
Full Version: Why Not to speed up Firefox
QUOTE (bitbizket @ Aug 12 2007, 01:06 AM) 
"Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once"
It's like raping the servers dude..FF2 is cap to 8 at max.
Imagine a door way big enough for 8 persons is force to 30 people at once..that will chocked the servers if everyone does that..
It's like raping the servers dude..FF2 is cap to 8 at max.
Imagine a door way big enough for 8 persons is force to 30 people at once..that will chocked the servers if everyone does that..
^^^^ What bitbizket said
Believe me you wouldn't all think this was such a brilliant idea if you were trying to tune a webserver with limited resources.
I have never touched anything in Firefox and it works fine for me.
Making a large number of requests at servers is not good practice. Just ends up putting unneeded strain on the server and if it is a smaller server, will end up slowing or stopping things for everyone.
Making a large number of requests at servers is not good practice. Just ends up putting unneeded strain on the server and if it is a smaller server, will end up slowing or stopping things for everyone.
yeah kcuf what all those other people say i could care less about "The Man's" sever and how well its working for "HIM" Its all about me
Thanks for the help noticed a big increase in speed thanks
Thanks for the help noticed a big increase in speed thanks
Ok for the hard of thinking amongst you.
You regard websites as a service that should cost you nothing, well two people pay for this one it's costing $3400 a year at the moment and a considerable amount of time wasted tuning the webserver so it can cope with the demands on it, people jacking up the requests they make doesn't help and I'm singularly unimpressed that your think owning the "Man" is ok. Lets put it this way .... how would you like to find your ip in the sites blocklist would that be pwned satisfactorily ?
You regard websites as a service that should cost you nothing, well two people pay for this one it's costing $3400 a year at the moment and a considerable amount of time wasted tuning the webserver so it can cope with the demands on it, people jacking up the requests they make doesn't help and I'm singularly unimpressed that your think owning the "Man" is ok. Lets put it this way .... how would you like to find your ip in the sites blocklist would that be pwned satisfactorily ?
Thanx Alot Benji.....
Works Super fast now (makes one wonder why Firefox choice the standard to run so slow??)
Wonderful Tweak.....Very happy now.
Works Super fast now (makes one wonder why Firefox choice the standard to run so slow??)
Wonderful Tweak.....Very happy now.
@ GFire here's one good reason
QUOTE (ABBANDON @ Aug 13 2007, 11:12 PM)
Ok for the hard of thinking amongst you.
You regard websites as a service that should cost you nothing, well two people pay for this one it's costing $3400 a year at the moment and a considerable amount of time wasted tuning the webserver so it can cope with the demands on it, people jacking up the requests they make doesn't help and I'm singularly unimpressed that your think owning the "Man" is ok. Lets put it this way .... how would you like to find your ip in the sites blocklist would that be pwned satisfactorily ?
You regard websites as a service that should cost you nothing, well two people pay for this one it's costing $3400 a year at the moment and a considerable amount of time wasted tuning the webserver so it can cope with the demands on it, people jacking up the requests they make doesn't help and I'm singularly unimpressed that your think owning the "Man" is ok. Lets put it this way .... how would you like to find your ip in the sites blocklist would that be pwned satisfactorily ?
The original how to speed up firefox topic has been removed for all those of you who think you are so clever it is YOU that cause this site problems at it's busy time, and note if we chose to we could detect who has done this and have Apache kick your ip.
honestly, if you want a faster firefox, uninstall it. get a better browser, from stock settings opera has always run faster, downloads, page grabbing, history searching, everything is faster, granted if you enable all of it's options it uses more resources, except for the firefox memory leaks, no one can beat those
just by simply setting the redraw to 1 second and cache higher, you will notice much faster browsing speeds, i've left the default connections to 8 this whole time and never noticed a problem
just by simply setting the redraw to 1 second and cache higher, you will notice much faster browsing speeds, i've left the default connections to 8 this whole time and never noticed a problem
How does one change it back to the original settings? Just uninstall than re-install?
The easiest option is to set it to default by typing about:config in Firefox browser address bar.
Instantly Firefox displays a large range of preferences sorted alphabetically.
Run through the menu adjusting the status each back to default.
Heres a sample.
network.http.max-connections [Integer] (24)
- This setting determines how many simultaneous HTTP connections can be made by Firefox. The default is already 24. The maximum is 65535, but remember that by raising this setting you are only raising the maximum possible number of connections. You aren't forcing Firefox to increase the actual number of connections it makes every time; if your system actually attempted to force 300 connections to open at once for example it would likely slow down to a crawl.
network.http.max-connections-per-server [Integer] (8)
- This setting determines how many simultaneous connections can be made to a single server. The default is 8, note that raising this setting to a high value (in conjunction with a high value for the network.http.max-persistent-connections-per-.* settings below) may be construed as a DDoS (Distributed Denial of Service) attack by some servers and your connection may be refused. Aside from that, it may actually slow down your browsing and it's also poor netiquette to hammer people's servers with dozens of connections from a single machine, so I strongly suggest that you keep this value sane.
network.http.max-persistent-connections-per-proxy [Integer] (4)
- If you are connected to a proxy, this setting determines how many connections to keep alive at any time. The default is 4. As mentioned raising this to a very high value will put additional stress on the proxy server and may ultimately result in slower browsing for everyone on the proxy and/or a refused connection.
network.http.max-persistent-connections-per-server [Integer] (2)
- If you are not connected to a proxy, this setting determines how many connections to a single server to keep alive at any time. The default is 2. As mentioned raising this to a very high value will put stress on the particular website server you are connected to and will either result in a refused connection, or slower response times from the web page for every person trying to connect to it. Do not raise this value to one which is very high as it is inconsiderate and counter-productive if everyone does so.
network.http.pipelining [Boolean] (False)
- If set to True, this setting uses the new HTTP Pipelining feature supported by some servers and proxies. This can improve browsing speeds, however because the feature is not supported by all servers you may experience problems. I recommend setting this to True and only disabling it if you experience such problems as refused connections or unusual behavior.
network.http.proxy.pipelining (Boolean) (False)
- This feature performs exactly as per the above (true to enable, false to disable), albeit it applies to connections over a proxy.
network.http.pipelining.maxrequests [Integer] (4)
- This setting determines the maximum number of requests to send when using the HTTP Pipelining feature (see above). The default is 4, and the maximum possible is 8 (higher values are ignored).
network.http.proxy.keep-alive (Boolean) (False)
- Setting this to true enables the use of persistent connections over proxy servers. This can provide more efficient connections with legacy servers as it streamlines the process, e.g. fewer TCP connections/packets and pipelining support. In the event of problems arising with legacy servers set this to false. HTTP/1.1 supports persistent connections by default.
network.http.proxy.pipelining [Boolean] (False)
- If set to True, this setting enables the HTTP Pipelining feature (see network.http.pipelining above) for proxy servers. This can improve browsing speeds, however because the feature is not supported by all proxies you may experience problems, such as refused connections, longer page loading times, or unusual behavior.
Instantly Firefox displays a large range of preferences sorted alphabetically.
Run through the menu adjusting the status each back to default.
Heres a sample.
network.http.max-connections [Integer] (24)
- This setting determines how many simultaneous HTTP connections can be made by Firefox. The default is already 24. The maximum is 65535, but remember that by raising this setting you are only raising the maximum possible number of connections. You aren't forcing Firefox to increase the actual number of connections it makes every time; if your system actually attempted to force 300 connections to open at once for example it would likely slow down to a crawl.
network.http.max-connections-per-server [Integer] (8)
- This setting determines how many simultaneous connections can be made to a single server. The default is 8, note that raising this setting to a high value (in conjunction with a high value for the network.http.max-persistent-connections-per-.* settings below) may be construed as a DDoS (Distributed Denial of Service) attack by some servers and your connection may be refused. Aside from that, it may actually slow down your browsing and it's also poor netiquette to hammer people's servers with dozens of connections from a single machine, so I strongly suggest that you keep this value sane.
network.http.max-persistent-connections-per-proxy [Integer] (4)
- If you are connected to a proxy, this setting determines how many connections to keep alive at any time. The default is 4. As mentioned raising this to a very high value will put additional stress on the proxy server and may ultimately result in slower browsing for everyone on the proxy and/or a refused connection.
network.http.max-persistent-connections-per-server [Integer] (2)
- If you are not connected to a proxy, this setting determines how many connections to a single server to keep alive at any time. The default is 2. As mentioned raising this to a very high value will put stress on the particular website server you are connected to and will either result in a refused connection, or slower response times from the web page for every person trying to connect to it. Do not raise this value to one which is very high as it is inconsiderate and counter-productive if everyone does so.
network.http.pipelining [Boolean] (False)
- If set to True, this setting uses the new HTTP Pipelining feature supported by some servers and proxies. This can improve browsing speeds, however because the feature is not supported by all servers you may experience problems. I recommend setting this to True and only disabling it if you experience such problems as refused connections or unusual behavior.
network.http.proxy.pipelining (Boolean) (False)
- This feature performs exactly as per the above (true to enable, false to disable), albeit it applies to connections over a proxy.
network.http.pipelining.maxrequests [Integer] (4)
- This setting determines the maximum number of requests to send when using the HTTP Pipelining feature (see above). The default is 4, and the maximum possible is 8 (higher values are ignored).
network.http.proxy.keep-alive (Boolean) (False)
- Setting this to true enables the use of persistent connections over proxy servers. This can provide more efficient connections with legacy servers as it streamlines the process, e.g. fewer TCP connections/packets and pipelining support. In the event of problems arising with legacy servers set this to false. HTTP/1.1 supports persistent connections by default.
network.http.proxy.pipelining [Boolean] (False)
- If set to True, this setting enables the HTTP Pipelining feature (see network.http.pipelining above) for proxy servers. This can improve browsing speeds, however because the feature is not supported by all proxies you may experience problems, such as refused connections, longer page loading times, or unusual behavior.
As with most tweaks, not alot of study goes into them. People just believe it works because they read it on the intraweb. Probably didn't notice that it loaded faster after the tweak because they reloaded a page in "CACHE" and assumed it was better.
thnaks, very useful !! .. 
stop raping these servers >.<
jus get a bttr connection, bttr than having ur ip booted right?
and like maz said, get opera, it runs faster, and its easier, and i love it.
jus get a bttr connection, bttr than having ur ip booted right?
and like maz said, get opera, it runs faster, and its easier, and i love it.
Well after reading this post I`ll not change it again !!!
thanks for the INFO.
thanks for the INFO.
QUOTE (bitbizket @ Nov 14 2007, 08:02 PM)
The easiest option is to set it to default by typing about:config in Firefox browser address bar.
Instantly Firefox displays a large range of preferences sorted alphabetically.
Run through the menu adjusting the status each back to default.
Heres a sample.
network.http.max-connections [Integer] (24)
- This setting determines how many simultaneous HTTP connections can be made by Firefox. The default is already 24. The maximum is 65535, but remember that by raising this setting you are only raising the maximum possible number of connections. You aren't forcing Firefox to increase the actual number of connections it makes every time; if your system actually attempted to force 300 connections to open at once for example it would likely slow down to a crawl.
network.http.max-connections-per-server [Integer] (8)
- This setting determines how many simultaneous connections can be made to a single server. The default is 8, note that raising this setting to a high value (in conjunction with a high value for the network.http.max-persistent-connections-per-.* settings below) may be construed as a DDoS (Distributed Denial of Service) attack by some servers and your connection may be refused. Aside from that, it may actually slow down your browsing and it's also poor netiquette to hammer people's servers with dozens of connections from a single machine, so I strongly suggest that you keep this value sane.
network.http.max-persistent-connections-per-proxy [Integer] (4)
- If you are connected to a proxy, this setting determines how many connections to keep alive at any time. The default is 4. As mentioned raising this to a very high value will put additional stress on the proxy server and may ultimately result in slower browsing for everyone on the proxy and/or a refused connection.
network.http.max-persistent-connections-per-server [Integer] (2)
- If you are not connected to a proxy, this setting determines how many connections to a single server to keep alive at any time. The default is 2. As mentioned raising this to a very high value will put stress on the particular website server you are connected to and will either result in a refused connection, or slower response times from the web page for every person trying to connect to it. Do not raise this value to one which is very high as it is inconsiderate and counter-productive if everyone does so.
network.http.pipelining [Boolean] (False)
- If set to True, this setting uses the new HTTP Pipelining feature supported by some servers and proxies. This can improve browsing speeds, however because the feature is not supported by all servers you may experience problems. I recommend setting this to True and only disabling it if you experience such problems as refused connections or unusual behavior.
network.http.proxy.pipelining (Boolean) (False)
- This feature performs exactly as per the above (true to enable, false to disable), albeit it applies to connections over a proxy.
network.http.pipelining.maxrequests [Integer] (4)
- This setting determines the maximum number of requests to send when using the HTTP Pipelining feature (see above). The default is 4, and the maximum possible is 8 (higher values are ignored).
network.http.proxy.keep-alive (Boolean) (False)
- Setting this to true enables the use of persistent connections over proxy servers. This can provide more efficient connections with legacy servers as it streamlines the process, e.g. fewer TCP connections/packets and pipelining support. In the event of problems arising with legacy servers set this to false. HTTP/1.1 supports persistent connections by default.
network.http.proxy.pipelining [Boolean] (False)
- If set to True, this setting enables the HTTP Pipelining feature (see network.http.pipelining above) for proxy servers. This can improve browsing speeds, however because the feature is not supported by all proxies you may experience problems, such as refused connections, longer page loading times, or unusual behavior.
Instantly Firefox displays a large range of preferences sorted alphabetically.
Run through the menu adjusting the status each back to default.
Heres a sample.
network.http.max-connections [Integer] (24)
- This setting determines how many simultaneous HTTP connections can be made by Firefox. The default is already 24. The maximum is 65535, but remember that by raising this setting you are only raising the maximum possible number of connections. You aren't forcing Firefox to increase the actual number of connections it makes every time; if your system actually attempted to force 300 connections to open at once for example it would likely slow down to a crawl.
network.http.max-connections-per-server [Integer] (8)
- This setting determines how many simultaneous connections can be made to a single server. The default is 8, note that raising this setting to a high value (in conjunction with a high value for the network.http.max-persistent-connections-per-.* settings below) may be construed as a DDoS (Distributed Denial of Service) attack by some servers and your connection may be refused. Aside from that, it may actually slow down your browsing and it's also poor netiquette to hammer people's servers with dozens of connections from a single machine, so I strongly suggest that you keep this value sane.
network.http.max-persistent-connections-per-proxy [Integer] (4)
- If you are connected to a proxy, this setting determines how many connections to keep alive at any time. The default is 4. As mentioned raising this to a very high value will put additional stress on the proxy server and may ultimately result in slower browsing for everyone on the proxy and/or a refused connection.
network.http.max-persistent-connections-per-server [Integer] (2)
- If you are not connected to a proxy, this setting determines how many connections to a single server to keep alive at any time. The default is 2. As mentioned raising this to a very high value will put stress on the particular website server you are connected to and will either result in a refused connection, or slower response times from the web page for every person trying to connect to it. Do not raise this value to one which is very high as it is inconsiderate and counter-productive if everyone does so.
network.http.pipelining [Boolean] (False)
- If set to True, this setting uses the new HTTP Pipelining feature supported by some servers and proxies. This can improve browsing speeds, however because the feature is not supported by all servers you may experience problems. I recommend setting this to True and only disabling it if you experience such problems as refused connections or unusual behavior.
network.http.proxy.pipelining (Boolean) (False)
- This feature performs exactly as per the above (true to enable, false to disable), albeit it applies to connections over a proxy.
network.http.pipelining.maxrequests [Integer] (4)
- This setting determines the maximum number of requests to send when using the HTTP Pipelining feature (see above). The default is 4, and the maximum possible is 8 (higher values are ignored).
network.http.proxy.keep-alive (Boolean) (False)
- Setting this to true enables the use of persistent connections over proxy servers. This can provide more efficient connections with legacy servers as it streamlines the process, e.g. fewer TCP connections/packets and pipelining support. In the event of problems arising with legacy servers set this to false. HTTP/1.1 supports persistent connections by default.
network.http.proxy.pipelining [Boolean] (False)
- If set to True, this setting enables the HTTP Pipelining feature (see network.http.pipelining above) for proxy servers. This can improve browsing speeds, however because the feature is not supported by all proxies you may experience problems, such as refused connections, longer page loading times, or unusual behavior.
As a former tweaker
I have just gone through and reset as above and definitely can tell a difference with most sites I have checked so far. 
cheers bitbizket
Thanks for the info everyone. Generally I for speeding things up, but not at any cost. 
thanks for sharing
QUOTE (Mazuki @ Oct 29 2007, 03:27 PM)
honestly, if you want a faster firefox, uninstall it. get a better browser, from stock settings opera has always run faster, downloads, page grabbing, history searching, everything is faster, granted if you enable all of it's options it uses more resources, except for the firefox memory leaks, no one can beat those
just by simply setting the redraw to 1 second and cache higher, you will notice much faster browsing speeds, i've left the default connections to 8 this whole time and never noticed a problem
just by simply setting the redraw to 1 second and cache higher, you will notice much faster browsing speeds, i've left the default connections to 8 this whole time and never noticed a problem
i been using firefox for years and never had problems with speed takes about 2 sec. for any page to load but i think i will try Opera heard of it but never gave it any thought
EDIT: So i downloaded Opera and so far i like it looks and feels like FF but is there anyway to import my FF passwords into opera?
and also is there a addon to export passwords from opera like FF has
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.