Reading the Mozilla forums, I found something that makes it render pages faster. Add this to your own prefs.js (should be somewhere under the .mozilla/ folder in your home directory):

Code:

user_pref("nglayout.initialpaint.delay", 0);

By default Mozilla comes with it set to 500 and in Phoenix it is set to 250 (that's why Phoenix feels faster when rendering)
I've been using for a few weeks now and definitely Mozilla feels much faster, and I haven't found any side effect yet

PS.: Don't ask me about any technical reason for this. I simply found it, tested it and noticed the increase of speed...

I would imagine the delay is to wait for the entire html to be downloaded so the page doesn't adjust in the eyes of the view as <table> tags get completed._________________Want Free games?
Free Gamer - open source games list & commentary

Well, one thing I'd like to point out is that this doesn't really make Mozilla render faster. It just makes the user feel that the page rendered faster because the time it takes between mozilla gets the last chunk of data and when it shows it has been reduced to 0. It's the same idea behind the preemptive patches for the kernel: they don't make it run faster but they make the whole system feel more responsive and snappier (specially the X environment)

You can have more detailed technical information about it if you follow the link to the BugZilla page _________________O God, Thou art in Heaven...
...please stay there!

Reading the Mozilla forums, I found something that makes it render pages faster. Add this to your own prefs.js (should be somewhere under the .mozilla/ folder in your home directory):

Code:

user_pref("nglayout.initialpaint.delay", 0);

By default Mozilla comes with it set to 500 and in Phoenix it is set to 250 (that's why Phoenix feels faster when rendering)
I've been using for a few weeks now and definitely Mozilla feels much faster, and I haven't found any side effect yet

PS.: Don't ask me about any technical reason for this. I simply found it, tested it and noticed the increase of speed...

It's the same idea behind the preemptive patches for the kernel: they don't make it run faster but they make the whole system feel more responsive and snappier

Well, kind of, not really. User-space threads (like X) work in a pre-emptive fashion, as they have from day one; kernel-space threads are now subject to a similar scheduling system, meaning that user-space threads get control in a more orderly fashion and that kernel blocks are less of an issue._________________I don't believe in witty sigs.

@phunkphorce: Sure, but why the hell mozilla doesn't respect changes made by users!? Thx anyway! Loading sites from slow servers is smarter now, if you know you want to click on one already shown link.

It's the same idea behind the preemptive patches for the kernel: they don't make it run faster but they make the whole system feel more responsive and snappier

Well, kind of, not really. User-space threads (like X) work in a pre-emptive fashion, as they have from day one; kernel-space threads are now subject to a similar scheduling system, meaning that user-space threads get control in a more orderly fashion and that kernel blocks are less of an issue.

Well, maybe the example I chose wasn't really the best one... I simply tried to mean that it's not that Mozilla renders pages fasters but that it seems that it renders faster, just because it shows something faster. I remember that back in the days when I was at the university studying operating systems, there were several different ways to measure the efficiency of an operating system, and as far as I remember one of them was based on how fast a process can show some data to the user (or something like that )

I think in this case is the same. Setting that value to 0, as I have suggested, doesn't Mozilla make faster at all, but you get to see things faster even if Mozilla hasn't finished loading the page. For example everytime I reload this page in the forums I can see how it is built and it is redrawn at least a couple of times, kind of what Explorer does. So, my own subjective impression is that it works faster, just as the X-Window feels faster and snappier when all the preemption patches are applied in your kernel.

maybe your right, maybe your wrong.. all i know is it put it in the existing .js file while moz wasnt running and then i started moz and it was quicker... so then i opened the .js file that i edited and YES it was still there.. although it had moved about twenty lines down the file.. which is a little strange but who cares its still there and thats all i really care about _________________Blizzard you suck.