Closed
Bug 22101
Opened 25 years ago
Closed 25 years ago
[perf] investigate imap message loading performance
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M14
People
(Reporter: Bienvenu, Assigned: mscott)
References
Details
We're at least three times slower loading imap messages than 4.5 - need to
figure out why.
Reporter | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•25 years ago
|
||
accepting
Reporter | ||
Updated•25 years ago
|
Target Milestone: M14
Reporter | ||
Comment 2•25 years ago
|
||
mscott's work on loading the message with one url has sped this up enormously, I
think partly because layout and libmime can start working on the message while
the imap code is waiting for the rest of message to get downloaded from the
server. I think what he's done may be sufficient.
Reporter | ||
Updated•25 years ago
|
Summary: investigate imap message loading performance → [perf] investigate imap message loading performance
Whiteboard: [perf]
Reporter | ||
Comment 3•25 years ago
|
||
move perf to summary
Reporter | ||
Updated•25 years ago
|
Assignee: bienvenu → mscott
Status: ASSIGNED → NEW
Reporter | ||
Comment 4•25 years ago
|
||
Reassign to Scott, so he can mark it fixed - I think we're OK now.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•25 years ago
|
||
the new msg display stuff + hooking imap up to the memory cache = one fixed bug.
QA Contact: suresh → stephend
What was our time back in 1999, when this was filed?? IMAP loading of a message
could be improved, but it's not 3x as slow as 4.x I do have a bug filed
against folder loading though. Can I verify this?
Loading messages is fine, it's just our displaying (trees, XUL) that could use
some more lovin'. Marking VERIFIED, our main perf bug is 63759 (tracker, meta).
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•