Increase Firefox Speed?

27
2013-07
  • Questioner

    Found a way to really speed up Firefox - I've implemented it and noticed serious speed improvements. Can anyone comment ?

    1. Type in the Firefox address about:config
    2. Accept the Warning notification and continue
    3. At the top of the page will be a filter – search for, and adjust, the following settings:

    network.http.pipelining: true
    network.http.proxy.pipelining: true
    network.http.max-connections: 50
    network.http.max-connections-per-server: 40
    network.http.max-persistent-connections-per-proxy: 20
    network.http.max-persistent-connections-per-server: 10
    network.http.pipelining.maxrequests: 20

    1. Then right-click anywhere in a blank space and select New –> Integer
    2. Name this integer “nglayout.initialpaint.delay” and set its value to 0.
    3. Right-click again anywhere in a blank space and select New –> Boolean
    4. Name this boolean “config.trim_on_minimize” and set its value to True.
    5. Now in the Icon Tray, right-click on the Mozilla Firefox Icon and select Properties
    6. Under “Target”, you will see the line “C:\Program Files\Mozilla Firefox\firefox.exe”
    7. Change this line to “C:\Program Files\Mozilla Firefox\firefox.exe” /Prefetch:1″
    8. Ensure that there is a space i.e. \firefox”(space)/Prefetch:1″

    Got this off a website I found via Twitter (removed link; see history if you care...)

  • Answers
  • Brandon

    Take a look at this article by Asa Dotzler (a Mozilla dev). The downside to this is that not all websites will display correctly, and that while you see some content much faster than you normally would, overall the page takes longer to display.

    A long time ago, I also found on another site a note which mentioned that changing the network settings also makes more requests than normal to the web server, and has led to websites banning people who use this hack because of the strain it puts on their servers.

  • Blorgbeard

    Most if not all of these options will be tradeoffs.

    A good reference is http://kb.mozillazine.org/Category:Preferences

  • koenigdmj

    It's probably overkill, but a friend of mine copies his ~/.mozilla to a tmpfs, runs Firefox on that directory, and copies it back every couple minutes in case the kernel panics.

  • DWilliams

    The downside to pipelining is that is puts additional strain on the webserver you're requesting pages from. Just one person doing this isn't a big problem, but lots of people use this tweak. This is definitely a large contributor to the "Slashdot effect" where a smaller site will crash upon being linked to by a very popular site (like Slashdot, Digg, Reddit, etc etc). A ton of people are directed to that site, and if even 25% of them are pipelining than the server strain starts to increase almost exponentially.

    Also, the numbers in those instructions are too high. Firefox caps the number of simultaneous HTTP requests anyway. I recall reading that the maximum was something like 8 or 16, but I could be wrong.

  • Mitchel Sellers

    I personally have been using the FireFox extension FasterFox and it has made a marked improvement in my browser experience. I'm not 100% sure what all it changes, but it is a very easy process since it is a simple add-on.

  • WindowsEscapist

    The main problem here is pipelining. (That nglayout.initialpaint.delay is how fast Firefox displays data it has already received.)

    Basically, when you set your pipelining data (non-proxy) to something like 50 (which is overkill), you are using the server-side connection speed of 50 different people. There's no downside for you, but the places you are going to will suffer.

    Proxy pipelining is a little bit different, but it's basically the same issue. You'll place more strain on the proxy (bad if it's a public proxying service, ok if the proxy is your personal computer or only servicing a small number of people anyway).

    If you really need the speed boost then you can probably set your pipelining values to something like 2 or 3, but really you don't need pipelining on at all. Those extra requests are wasted data in the end (server-side), because it will end up sending you multiple copies of your data.

    Also, your internet connection as a whole might be adversely affected, because you'll be transferring much more data total. Your torrenting, downloading, updating, etc. might be affected.


  • Related Question

    configuration - Increasing download speed for torrents?
  • pramodc84

    Can you please list out any torrent client configuration to get max out of available net speed?


  • Related Answers
  • pelms

    Try these tips from TorrentFreak.

    The factor that made the most difference for me was to limit the upload speed.
    For instance, for my 2Mb/s connection I limited the upload speed to about 1/15 of the maximum download rate, i.e. an upload rate of 136kb/s (17kB/s) - TorrentFreak recommends setting the upload speed to about 80% of the measured maximum upload rate. If the upload is set too high it will slow down the downloads since they need to use some upload capacity for requests.

    P.S. Of course I also set the torrent client to switch to unlimited upload speeds once downloads are complete so I can seed the torrents more quickly.

  • Omar Abid

    There are three main things that may help.

    1. If you are connecting from behind a router make sure the port you are connecting for the torrents has been forwarded (check here for guides: PortForward.com)

    2. While looking for downloads try to not get something redicualisly large.
      Ie. if i want to get a movie for my iPhone i wouldn't get the 8Gig copy over the 1Gig copy.

    3. Look for the amount of seeders to leechers. Seeders are people who have already downloaded the file and are sharing it for others to download. Leechers are the people who are downloading the file as well.
      So i wouldn't even bother getting a file that has 1 seeder and 20 leechers.

  • Moshe

    Keep in mind that some ISPs are putting a cap on the maximum speed you can get via torrent clients. These ISPs are detecting the protocol torrent clients are using, and slow it down on purpose.

    You should consider using a client using the newer uTP protocol (such as uTorrent's beta) for best performance.

    You can read more about it here.

  • salmonmoose

    For underground content (the stuff you shouldn't be downloading) try to find a private tracker, they'll give amazing speeds as everyone there is desperate to upload.

    For legitimate traffic - you shouldn't have a problem, unless someone creates a new torrent for an existing file.

    Don't hammer your outbound bandwidth - set it at 50-75% of your capacity, a clogged out-bound channel will nerf your inbound traffic. Also, don't run too many torrents at once.