Run Firefox faster
03-16-2009, 02:17 PM
#1
Run Firefox faster
Just did this, wanted to spread the wealth if you didn't know it already.
Firefox pages runs faster by allowing multiple connections so it can download more than one file at a time.
Here’s something for broadband people that will really speed Firefox up. It’s only useful for broadband users, so if you’re still on dial-up you can just skip this one for now.
Directions:
1.Type “about:config” into the address bar and hit return. Scroll down and look for the following entries:
network.http.pipelining
network.http.proxy.pipelining
network.http.pipelining.maxrequests
Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.
2. Alter the entries as follows:
Set “network.http.pipelining” to “true”
Set “network.http.proxy.pipelining” to “true”
Set “network.http.pipelining.maxrequests” to some number like 30. This means it will make 30 requests at once.
3. Lastly right-click anywhere and select New-> Integer. Name it “nglayout.initialpaint.delay” and set its value to “0″. This value is the amount of time the browser waits before it acts on information it receives.
If you’re using a broadband connection you’ll load pages MUCH faster now!
Enjoy!
Here’s something for broadband people that will really speed Firefox up. It’s only useful for broadband users, so if you’re still on dial-up you can just skip this one for now.
Directions:
1.Type “about:config” into the address bar and hit return. Scroll down and look for the following entries:
network.http.pipelining
network.http.proxy.pipelining
network.http.pipelining.maxrequests
Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.
2. Alter the entries as follows:
Set “network.http.pipelining” to “true”
Set “network.http.proxy.pipelining” to “true”
Set “network.http.pipelining.maxrequests” to some number like 30. This means it will make 30 requests at once.
3. Lastly right-click anywhere and select New-> Integer. Name it “nglayout.initialpaint.delay” and set its value to “0″. This value is the amount of time the browser waits before it acts on information it receives.
If you’re using a broadband connection you’ll load pages MUCH faster now!
Enjoy!
Reply
0
0
03-16-2009, 02:23 PM
#3
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,019
Total Cats: 6,587
+1. It took a while to warm up to, but Chrome is a man's browser. Every tab appears as a separate instance in task manager so you can see the memory and CPU usage of each page. It also has its own built-in task manager, which further breaks down the processes, showing the plugins separate from the tabs. Shockwave hogging too much CPU time? Just kill it and move on.
Absolutely the best browser since Lynx.
Absolutely the best browser since Lynx.
Reply
0
0
03-16-2009, 08:33 PM
#10
Reply
0
0
03-16-2009, 08:46 PM
#12
Reply
0
0
03-16-2009, 09:18 PM
#13
Originally Posted by Google Chrome Help
For times when you want to browse in stealth mode, for example, to plan surprises like gifts or birthdays, Google Chrome offers the incognito browsing mode. Webpages that you open and files downloaded while you are incognito won't be logged in your browsing and download histories...
Set browsers to "****"!
Reply
0
0
03-17-2009, 09:12 AM
#19
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,019
Total Cats: 6,587
I've played the browser game for years. My first exposure to the web was via Lynx, since at the time (mid 90s) my only connection was via shell access to the VAX (VMS) and Alpha (Unix) machines on the UF campus. Which was fine, since I was still using DOS as my primary OS (I loaded Windows only to do WYSIWYG word processing) so I just kept using ProComm Plus, the same terminal I'd been running since the BBS era.
In '96 I believe it was, I cam across TIA, and decided to give it a shot. We complied and ran it on one of the Vaxen, loaded Trumpet Winsock on the client side, and downloaded Mosaic.
Then Netscape Navigator happened, so we jumped to that. About that time, Netscape also released an email client, so we figured out how to get SMTP out of the Unix cluster, and downloaded that as well. Goodbye, Pine.
Netscape was the browser of choice for quite a long time, until the early 00s when I decided to give Opera a try. Love at first sight. Mouse Gestures was what did it for me, since at the time mice didn't have side buttons. But with time, it seemed like the browser was being incompatible with more and more sites, and was crash-prone.
Enter FireFox. The world's best bookmark manager, bar none. And it remembers which tabs I had open after I close it. K-rad. Ran this for years, but like many of you, found that over time it turned into more and more of a resource hog. Not unusual at all to find it parked in > 500MB of core. It was FireFox, not Adobe Premiere, that made me upgrade to 2GB on my primary system.
And now we have Chrome. At first, I hated it. No menu bar? WTF kind of crippled **** was this? But I've grown to love it. It's fast, reliable, compatible, and once you figure out where the eggs are, it turns out to be a real man's browser. It's the built-in task manager that does it for me.
Hmmm. Downloading.
Reply
0
0
