Firefox Tuning
February 21st, 2004, 8:02 pm
or what is a good setting for dialup also?
i want to be able to view the images though also.....i normally tweak FF using about:config how do i make sure i have a user.js file (i created one by saying new text document...but it doesn't ever add anything to it) i really like FF and want to tweak it to run nice. Thanks P.S. almost forgot unlike some of you guys, i have a slow pc, 450Mhz...so the tweaks for a fast pc i don't know if they will work or not.
February 22nd, 2004, 12:54 am
I don't know it exactly, but I think these two are not longer used with the new DM: browser.download.progressDnldDialog.keepAlive browser.download.useProgressDialogs Aside from that, you seem to have everything covered. There are no additional DM prefs I'd be aware of.
February 22nd, 2004, 1:03 am
great tips thanks a lot
personally I think firefox rips apart IE in terms of speed, it loads pages from net about 10-50% faster, but the real difference is cached pages, try this test. load up 3 differed net pages in different IE windows, then in each window load a second url, now in window 1 or 2 (not the most recent window very important) click on the back button, you will notice there is a pause for no reason of around 2-5 seconds, normally any images on the page have to be reloaded from net as well. with firefox using back and forward it is always instant for me, and with over 10 tabs open 
thats the real speed improvement in my book.
February 22nd, 2004, 1:08 am
If you have problems creating a user.js, you should take a look at the ChromEdit extension. It allows you to edit all your user configuration files in the browser. With regard to your connection and system speed, try these sets: Rendering settings: user_pref("content.max.tokenizing.time", 2250000); user_pref("content.notify.backoffcount", 5); user_pref("content.notify.interval", 750000); user_pref("content.notify.ontimer", true); user_pref("content.switch.threshold", 750000); user_pref("nglayout.initialpaint.delay", 750); or alternatively: user_pref("content.max.tokenizing.time", 3000000); user_pref("content.notify.backoffcount", 5); user_pref("content.notify.interval", 1000000); user_pref("content.notify.ontimer", true); user_pref("content.switch.threshold", 1000000); user_pref("nglayout.initialpaint.delay", 1000); Connection settings: user_pref("network.http.max-connections", 32); user_pref("network.http.max-connections-per-server", 8); user_pref("network.http.max-persistent-connections-per-proxy", 8); user_pref("network.http.max-persistent-connections-per-server", 4); user_pref("network.http.pipelining", true); user_pref("network.http.proxy.pipelining", true); Also try different settings for this pref (4, 6 8): user_pref("network.http.pipelining.maxrequests", 8); Also use this if it's okay on your system to cache pages served over a secure connection: user_pref("browser.cache.disk_cache_ssl", true); Use what gives you the best performance. If you don't see any improvement, just remove these settings both form user.js as well as from prefs.js.
February 22nd, 2004, 1:12 am
nglayout initial paint delay, what exactly does this do, 750 seems a high setting so is higher faster (default 250)
thanks
February 22nd, 2004, 1:31 am
I'll try to explain it to the best of my knowledge: it decides about when the first reflow attempt is made if (and only if) the page isn't rendered completely anyway before this delay. A page reflow consume precious CPU time, so if you delay it a little longer, the total page load time goes down and the page layout calculation is closer to its final state when the first reflow happens.
Furthermore, synchronizing this value with the content sink timings seems to give the best results on my system (and obviously on others, too). I also tried it with lower values both for the content sink timings and the initial paint delay, but lower settings for the content sink timings noticeably raised the total page load times on my system. Last edited by laszlo on February 22nd, 2004, 1:34 am, edited 1 time in total.
February 22nd, 2004, 1:34 am
ok thanks for the explanation, I have set my delay to 750 and made sure the releveant content values are in synch
February 29th, 2004, 4:53 am
So what are the definitive settings as of this moment for both dial up and broadband?
February 29th, 2004, 5:19 am
Good question... I have a 2Mbit DSL connection and right now I just added some pipelining options, I'll try to use the laszlo settings... Ciao,
Rigido.
February 29th, 2004, 5:30 am
my main box is down at the moment but the tweaks I did do helped I think.
February 29th, 2004, 5:38 am
Alrighty...did some tests on my Dial-up connection on a 1 ghz P3.
I would have to say that I got the best results from the actual user.js settings that laszlo uses.
Great results here with the 2250000 tokenizing value instead of the 3000000 for dialup users and keeping connections at 32 and NOT 48. If anybody can see what works best for broadband, please, tell us.
February 29th, 2004, 5:56 am
that mem cache setting is going to need a fair amount of ram, if you do more than browsing on your box.
I will post back for broadband results when my main pc is back should be tommorow.
February 29th, 2004, 5:56 am
Not sure whether my connection fails into broadband or dial-up - it ranges from 3kb/s on bad days to 100 kb/s(but it soon drops to 50kb/s). It's judged as ADSL here, but I don't think the Koreans, Singaporeans or almost anybody else in the world with broadband would agree with me.
 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b) Gecko/20050205 Firefox/1.0+
March 4th, 2004, 7:53 pm
Anybody have any settings for broadband that have been thoroughly tested?
March 4th, 2004, 10:11 pm
Tried these on Moz 1.6 with DSL (1500/384). Noticable improvement on websites I've tested in the past. Who is onlineUsers browsing this forum: No registered users and 2 guests |
|
