OS2 World.Com Forum

Subject  :  "Speed up" Firefox...
Author  :  RobertM
Date  :  04 Jan, 2007 on 03:10
Hey all,

Don't know how many others are suffering from slow page loads in FireFox on Warp/eCS... but the problem is actually page rendering (which is horrendously slow with the last few years of ports). The gang porting to OS/2 are trying to rectify it, but in the meantime, I have found some preference changes/additions that have helpe make FireFox, SeaMonkey, etc appear a lot faster on my system.

You may want to fool with the values a little depending on how fast your machine is (this one is 1.1GHz). Basically, it delays page rendering a bit - enough so that the whole document (on a fast connection) is already loaded in the browser, then laid out, and THEN rendered to the screen. It also affects rendering on pages where the content is not fully downloaded to the browser before screen rendering starts.

You may notice a 1 second delay on page loads (display) for minimal pages - but with how few minimal pages are out there, I dont mind. Also, on my system, even a minimal page (a frameset, 10 form values) still took longer to render, re-size, render, resize while getting the page from the server than the page delay I am using below.

YMMV

Hope this helps... it goes in your prefs.js - make sure the browser is closed when you put it in, otherwise the browser will overwrite the settings when it closes. OR you can manually enter each value using Preferential or similar Preferences editor while the browser is running.

Most of you probably wont have any of these in your prefs.js file - but since it is apparently in sorted order, you can double-check before you put them in. You CAN put them at the bottom of the file and the browser will order them the next time it is opened and closed.

Something else to keep in mind, if you have a Mozilla_Home directory set, you need to find the appropriate prefs.js file in those directories - the one in the browser directory (if it exists) is not the one the browser is using.

HTH,
Robert


user_pref("content.max.tokenizing.time", 3000000);
user_pref("content.notify.backoffcount", 5);
user_pref("content.notify.interval", 2000000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 2000000);
user_pref("nglayout.initialpaint.delay", 12120);

For the very curious, for details about what each does, just Google em...


Subject  :  ANOTHER NOTE... Re:"Speed up" Firefox...
Author  :  RobertM
Date  :  04 Jan, 2007 on 03:12
Another Note:

If you run your own web servers, you will also notice that the browser is retrieving data a lot quicker because it is not trying to render to the screen while it is still retrieving data...


Subject  :  Re:"Speed up" Firefox...
Author  :  melf mikaelelf@os2ug.se
Date  :  04 Jan, 2007 on 09:20
That had quite a good effect, thanks Robert!

---
/Mikael

Subject  :  Install Tips... Notes...
Author  :  RobertM
Date  :  04 Jan, 2007 on 18:16
First, back up prefs.js - easier to replace your modified version with the backup than find the keys you need to remove if your browser hangs after this. [These keys (though not included with them) supposedly work with every version of Seamonkey, Firefox, etc... so you shouldnt have a problem, but better safe than sorry.]


------------------------------------------------------------
For those of you editing the prefs.js directly, CLOSE THE BROWSER, THEN, just add the lines...

user_pref("content.max.tokenizing.time", 3000000);
user_pref("content.notify.backoffcount", 5);
user_pref("content.notify.interval", 2000000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 2000000);
user_pref("nglayout.initialpaint.delay", 12120);

...at the bottom of the file (or anywhere after the comments at the top). Save the file, then start the browser.


------------------------------------------------------------

For those of you using Preferential... do this...

-Wait for it to load the preferences tree...

-Right click on a blank area and select "Add New"

-Put in JUST the key value in the top field (ie: "content.max.tokenizing.time" - no quotes)

-Select INTEGER or BOOLEAN (all above are INT except "content.notify.ontimer" which is boolean).

-Put in the appropriate value (ie: 3000000 or TRUE, etc)

-You will be asked if you want to reload the preference tree before continuing. You can select NO (as long as you remember where you are so you dont forget a key or double enter one), its up to you whether or not you want to reload the tree after each entry.

-Once finished, close Preferential... at this point I close and restart the browser (which may not be necessary).

That's it!


Subject  :  Re:"Speed up" Firefox...
Author  :  RobertM
Date  :  04 Jan, 2007 on 18:17

melf (04 Jan, 2007 09:20):
That had quite a good effect, thanks Robert!

Very welcome. We have some clients we are installing eCS servers, and it looked kinda bad telling them how fast and stable it is and then fire up a web page that crawled... so glad I found these tips scattered about and glad to share them.

-R


Subject  :  Re:"Speed up" Firefox...
Author  :  RobertM
Date  :  04 Jan, 2007 on 18:21
Another Tip:


Some people have edited their maxconnections (and related) keys in Mozilla...

Some things to keep in mind... not every server out there is running OS/2 or Linux... some of them dont like 100 simultaneous connections . Also, many cable/dsl routers (ie: wired/wireless DDNS/DHCP routers) arent too happy handling/routing a few hundred connections at a time (when I open up Firefox, it loads near 10 tabs - with a maxconnections limit really high per server and for the browser).

Reducing those numbers to something more realistic may be helpful for some people, though I havent tested or benchmarked it... just seems like common sense (well, maybe not that common I hope... since I didnt think about it till last night).

-Robert


Subject  :  Re:"Speed up" Firefox...
Author  :  abwillis abwillis1@gmail.com
Date  :  04 Jan, 2007 on 21:24
A word of warning for those using Seamonkey. These are valid changes as well but if you use the mail/news component the nglayout.initialpaint.delay seems to adversely affects news posts when set to even 5000.

Powered by UltraBoard 2000 <www.ub2k.com>