Closed
Bug 9209
Opened 25 years ago
Closed 25 years ago
IMAP performance is very slow on large modified Inbox
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
M10
People
(Reporter: ppandit, Assigned: scottputterman)
References
Details
(Whiteboard: [Perf] [PR1])
Using release build (June 30) of seamonkey Talked with Scott Putterman about slow performance using IMAP after making many deletions from my Inbox using 4.7. Seamonkey could not load my Inbox because it was updating the Inbox.msf file one message at a time. The result was that either seamonkey hang (i.e. not responding) or the OS ran out virutal memory. Solution was to delete Inbox.msf file and just download current messages. Inbox contained approx. 1400 messages after deletions. Originally contained about 2200 messages. Par
Assignee | ||
Updated•25 years ago
|
Summary: IMAP performance is very slow on large modified Inbox → IMAP performance is very slow on large modified Inbox
Assignee | ||
Comment 1•25 years ago
|
||
This was painful because of the fact that I'm calling UpdateSummaryTotals in OnKeyDeleted. I had removed that for adding. I guess we could remove it for deleting also until we figure out how to batch message count change notifications.
We are pushing for performance by PR1, can you give this a Target Milestoneof M9 or M10 please.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M10
Assignee | ||
Comment 4•25 years ago
|
||
I'm putting M10 but I'd like to solve these sooner rather than later.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 5•25 years ago
|
||
Incremental writes should help this some too, if we're commiting after every delete notification.
We need to get IMAP performance up for PR1 so I added a note to the Status Whiteboard. Maybe this should also be a dogfood bug.
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•