PDA

View Full Version : Firefox and nglayout.initialpaint.delay value


Anusha
03-29-2007, 08:43 PM
I just found this:
Setting the initial paint delay at zero 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 zero or near zero, 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.

This one probably comes down to a combination of bandwidth, CPU speed, and personal preference. If it works for you, and you don't mind the side-effects, then great. Just note that what works for one person/system, may not work for another.

xRiica
10-22-2009, 12:29 AM
I just found this:

So whats a good value to pould it on then??