[Fasterfox] fasterfox - nglayout.initialpaint.delay
Larry
larry.pk at comcast.net
Sat Jan 7 09:17:07 EST 2006
according to the following article, setting
'nglayout.initialpaint.delay' to '0' (default in all but 'default'
preset) is, overall, a bad idea. 250 is recommended, even for broadband,
while higher values are suggested for lower bandwidth connections.
http://www.techspot.com/tweaks/firefox/firefox-9.shtml
partial quote...
------------------------
This is perhaps the most misunderstood setting in Firefox, with numerous
websites recommending you set this to 0 for fastest browsing. Somewhat
ironically this actually increases the total time rendering a webpage,
as explained by Asa Dotzler:
Setting the initial paint delay at 0, may get you some content on the
screen faster, but it's worth noting that it will dramatically slow down
the time it takes the entire page to display. Here's what's going on.
Gecko, Firefox's rendering engine, is trying to optimize between the
cost of waiting for a bit more data versus doing more painting and
reflows as new data comes in. Waiting a bit longer before it starts
painting the page gives Gecko a chance to receive more content before
chewing up CPU cycles to render and reflow the document. If you drop
this value down to 0 or near 0, that means you'll see the page start
displaying a bit earlier, but not having received much data in that
short interval, you'll have a lot more paint and reflow cycles to
complete rendering of the page.
So if you don’t care about overall rendering time then yes, setting this
to 0 can result in some content being displayed immediately.
-------------------------
just want to point that out :)
and thanks for making FF so easy to tweak! great ext.
larry
More information about the Fasterfox
mailing list