I did the following test on my Window NT box (733Mhz, 256MB) with yesterday
debug build:
1) out-comment the fcc menu in mesengercompose.xul
2) start mozilla
3) load messenger
4) create a new compose window (1st instance)
5) create a second compose window.
Effectively, we gain some time on the opening of the first compose window
but not on the other instance. The gain is:
first instance: with FCC= 6.80 sec, without FCC= 5.59 sec. Gain = 18%.
next instance: with FCC= 4.04 sec, without FCC= 4.02 sec. Gain = 0.5%.
That represent a great gain but unfortuatly, that append only the first
time you open a compose window.
JFD
Seth Spitzer wrote:
> I'm not sure how big of a performance win it would be, but we should see
> if it is possible to build up our file and copy menus *really* lazily.
>
> We have several such menus in the three pane, stand alone window, and
> one in compose.
>
> Right now, we set the datasources for those menus on loading of the xul
> (or they are hard coded in the xul, in the compose case), instead of
> when the user clicks on the menu item or toolbar button.
>
> I'm guessing it would speed up launch time for our windows, but would
> slow down the response time the first time you click.
>
> The one that is bugging me the most is the Fcc menu item in compose.
> I'm glad is there, but I've never use it. Why should I pay for it every
> time I create a message?
>
> Anyone interested in getting some numbers in how much gain this would
> be? You could do some timings, and then remove the fcc menu from the
> compose xul, and comment out the JS that initializes the data sources in
> the 3 pane and stand alone window and do the timings again. It would
> give us an estimate if there is something to win here.
>
> does anyone have the cycles to help investigate this?
>
> -Seth
