191149 - [perf] investigate caching the stand alone msg window

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[(not reading, please use [e-mail] instead)]

investigate caching the stand alone msg window

The reason caching is a big win for mail compose is the usage model of that window. 
It's typical to only have one compose window up at a time, and composing email
is a common thing to do.
(See http://www.mozilla.org/mailnews/arch/compose/cached.html for more details.)

But I'd discourage us doing this work until we have more data.

We should first see what's slowing down the stand alone msg window and see if we
could fix any of those issues first. 
Then determine the typical usage patterns and see if it makes sense to cache it.
And then see what caching the stand alone window would buy us, and then see if
it would be worth the complexity.

Improving performance is always important, but we have to make sure it is worth
it first.

At this point, I'd rather focus on bug fixes, finishing some of the new features
(like junk and mail views), and polish.

another this we need to look at is can we make new window time faster, across
the app?  This is another real issue, but a non-trivial one looked at
(repeatedly) by many people.

Comment 1

[(not reading, please use [e-mail] instead)]

futuring, no cycles for this.

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420