| |
|
Welcome to KnowledgeSutra - Dear Guest | |
Make Firefox 4x Faster.
Started by Benz1435, Mar 13 2005 06:48 PM
65 replies to this topic
#1
Posted 13 March 2005 - 06:48 PM
At one time Opera was the fastest available web browser, that time has ended. By default firefox has its turbo features shut off due to an error it used to display with tables. Use the tutorial below to add 200shots of nos to firefox, and increase page speeds up to 4 times, making firefox the fastest browser.
1) Open Firefox and on the address bar write about:config and hit enter
[find the string]
network.http.pipelining
double click and change the value to true
[find the string]
network.http.pipelining.maxrequests
double click and change the value to 34
[find the string]
browser.turbo.enabled
double click and change the value to true
now close and restart and see the new amazingly new speed of firefox...
1) Open Firefox and on the address bar write about:config and hit enter
[find the string]
network.http.pipelining
double click and change the value to true
[find the string]
network.http.pipelining.maxrequests
double click and change the value to 34
[find the string]
browser.turbo.enabled
double click and change the value to true
now close and restart and see the new amazingly new speed of firefox...
#2
Posted 13 March 2005 - 09:12 PM
I'm going to edit it now but it can go wrong so I'm going to put the default value of Mozilla (not Firefox). So if you need to put it the way it was:
[find the string]
network.http.pipelining
double click and change the value to false
[find the string]
network.http.pipelining.maxrequests
double click and change the value to 4
[find the string]
browser.turbo.enabled
double click and change the value to false
[find the string]
network.http.pipelining
double click and change the value to false
[find the string]
network.http.pipelining.maxrequests
double click and change the value to 4
[find the string]
browser.turbo.enabled
double click and change the value to false
#6
Posted 16 March 2005 - 06:14 AM
Benz1435, on Mar 14 2005, 02:48 AM, said:
At one time Opera was the fastest available web browser, that time has ended. By default firefox has its turbo features shut off due to an error it used to display with tables. Use the tutorial below to add 200shots of nos to firefox, and increase page speeds up to 4 times, making firefox the fastest browser.
1) Open Firefox and on the address bar write about:config and hit enter
[find the string]
network.http.pipelining
double click and change the value to true
[find the string]
network.http.pipelining.maxrequests
double click and change the value to 34
[find the string]
browser.turbo.enabled
double click and change the value to true
now close and restart and see the new amazingly new speed of firefox...
1) Open Firefox and on the address bar write about:config and hit enter
[find the string]
network.http.pipelining
double click and change the value to true
[find the string]
network.http.pipelining.maxrequests
double click and change the value to 34
[find the string]
browser.turbo.enabled
double click and change the value to true
now close and restart and see the new amazingly new speed of firefox...
#8
Posted 03 November 2005 - 12:15 AM
I was just wondering if these features were set the way they were for a reason... I mean the people at firefox probably set these this way because of a possible problem they ran into. Just curious if there was a possible security reason they set this up this way. Just my two cents..
#9
Posted 03 November 2005 - 07:04 AM
Very nice tip! It has made firefox a little bit faster...may be it is just my imagination...but as far as it seems to me that it has made the change...it is good
I think there are lots of utilities coming up which claim to make firefox faster..i think they use these strings to make it fast...that's what I can think of..may be they use a different technology all together to make it fast
#10
Posted 03 November 2005 - 07:20 AM
karlo, on Mar 14 2005, 10:22 PM, said:
That is part of what these alterations do. The changes listed above affect the way Firefox makes and receives requests to servers. It increases the number of requests that are allowed at a time. It has a fatter 'pipeline' to work with.
The 'slow load on start-up' can be improved by allowing Mozilla/firefox to stay-resident which means the "core" of the application begins when you power-on (start up) the computer and sits in the task tray near the clock on the bottom right hand of the window. Having Firefox start-up and stay resident allows for a quicker response when you start the browser because there has already been a bunch of the processes performed on machine start-up. The problem with this is your start-up takes a bit longer.
I might be wrong about all of this, but this is what I have been told.
#15
Posted 04 November 2005 - 02:22 AM
It's not possible to get DSL speeds on standard <= 56k dial-up, ever. You can do little things here and there to boost the speeds, but you cannot increase a 56k connection to 256k and above just by tweaking it. It's not as if dial-up is an intentionally restricted form of DSL than you can 'unlock' or anything. The physical build of the phone line has limitations of the speed of data it can transfer on the layer a dial-up modem uses, so it's not possible to exceed standard dial-up speeds by a significant amount.
This small hack make the page appear to load faster, but it seems to be just rendering the HTML quickly and then the images (and other content) later.
This small hack make the page appear to load faster, but it seems to be just rendering the HTML quickly and then the images (and other content) later.
#16
Posted 04 November 2005 - 12:39 PM
Spectre, on Nov 4 2005, 02:22 AM, said:
Yes I guess its something like that, since my CPU usage has gone up a little bit since I used this, still not a big problem tho...
#17
Posted 04 November 2005 - 09:51 PM
Well, I used this a while ago, there is another topic about this here on trap17. However, sometimes, the browser loaded wrong images. For instance, if there were two image on a website: cool.jpg and neo.jpg, neo.jpg could load where cool.jpg should have been loaded. This happened to me when loading sites with lots of images, so I changed it back to the normal, and now it works better...
#19
Posted 05 November 2005 - 01:18 AM
There is a catch with doing this little tweak to firefox. It makes more connections with the server you are on meaning it puts more load on the server. As one user with this tweak you act as if you were 8 people. So be kind on the servers you are on by not using this unless you really want the extra speed.
By the way, network.http.pipelining.maxrequests is hardwired to 8 so if you put it any higher than that it won't make a difference.
By the way, network.http.pipelining.maxrequests is hardwired to 8 so if you put it any higher than that it won't make a difference.
#21
Posted 22 January 2006 - 03:30 PM
Not the newest thing in the world, but if nothing else I can say that it really does work. Back when i did it everything loaded much faster, sites that would normally take a day and a half (deviantart.com for example) would load in a much more timely fashion.
though now-a-days i've been spoilt, since i've had my firefox "tweaked' for some time now.
though now-a-days i've been spoilt, since i've had my firefox "tweaked' for some time now.
Reply to this topic

1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
















