is it the time to reduce nglayout.initialpaint.delay value?

[orizng]

Its quite different time than 5 years ago now. is 250ms really necessary?

or is there other downsides I didn't realize?

[Fuziwuzi]

I have mine set to 0 (zero), it does make a noticeable difference to me.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008030405 Firefox/3.0b4pre ID:2008030405

[Omega X]

There is no real reason to reduce it. The browser paints less often at 250+ and can in some cases make the page render faster.

[KennS]

I seem to have two entries in about:config

nglayout.initialpaint.delay userset integer 50
nglayout.intialpaint.delay userset integer 1

There is a spelling difference between the two - is this on purpose???

I don't remember creating a variable by that name, and I've been using this profile for a long, long time.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008030405 Minefield/3.0b5pre ID:2008030405

[watervole02]

Neither entry exists by default, so you might have added nglayout.intialpaint.delay by mistake. There's no mozillazine knowledge base article for it.

[KennS]

Thanks Watervole02.

[RaiseMachine]

I seem to have two entries in about:config

nglayout.initialpaint.delay userset integer 50
nglayout.intialpaint.delay userset integer 1

There is a spelling difference between the two - is this on purpose???

No, you've just misspelled one of them.

The pref is still checked for: http://lxr.mozilla.org/seamonkey/source ... l.cpp#2468

There's no mozillazine knowledge base article for it.

http://kb.mozillazine.org/Nglayout.initialpaint.delay

[watervole02]

I was referring to nglayout.intialpaint.delay (without the i). nglayout.initialpaint.delay has a mozillazine article but nglayout.intialpaint.delay does not.

[kmc]

Mine is set to 100

[greenknight]

The default is a reasonable compromise between optimum for broadband and optimum for dialup. I'm on dialup, and I get faster rendering with a higher setting.

[Fuziwuzi]

The default is a reasonable compromise between optimum for broadband and optimum for dialup. I'm on dialup, and I get faster rendering with a higher setting.

That is reasonable. When I was on dialup and ISDN, having that set at 275 seemed to produce the best results. But now that I have extreme high speed broadband, setting it to zero is more efficient, I think.

[chob]

The nglayout.initialpaint.delay value tells firefox how long to wait after the server has responded before it starts to do layout/reflow/rendering. I'm not sure that a 250ms delay is going to have much effect on anything myself.

Setting it to 0 can mean as soon as the server sends the first byte, firefox tries to parse this and start layout, but of course it takes time for enough html to come back for firefox to render anything worth seeing.

Setting a value to 0 probably just means firefox chews a little more CPU time as it tried to render and relfow before having enough data to show anything meaningful. Although it probably gives the impression of being slightly more responsive because the page starts to render quarter of a second earlier.

[orizng]

I have no problem on either side

however, I think after so many changes in firefox 3. this value, when set to 0~100ms, have some significant impact on users (I dont know how many of them).

I just think we should re-evaluate it, even if eventually decide against a change.

[chob]

There's also other things that are related:
- http://kb.mozillazine.org/Content.notify.interval
- http://kb.mozillazine.org/Content.max.tokenizing.time
- http://kb.mozillazine.org/Content.switch.threshold