Closed Bug 9209 Opened 26 years ago Closed 26 years ago

IMAP performance is very slow on large modified Inbox

Categories

(MailNews Core :: Backend, defect, P3)

All
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 10689

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
Summary: IMAP performance is very slow on large modified Inbox → IMAP performance is very slow on large modified Inbox
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.
Hardware: PC → All
Whiteboard: [perf]
I assume this will be for all platforms.
Whiteboard: [perf] → [Perf]
We are pushing for performance by PR1, can you give this a Target Milestoneof M9 or M10 please.
Target Milestone: M10
I'm putting M10 but I'd like to solve these sooner rather than later.
Blocks: 9161
Status: NEW → ASSIGNED
Incremental writes should help this some too, if we're commiting after every delete notification.
Whiteboard: [Perf] → [Perf] [PR1]
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.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 10689 ***
Status: RESOLVED → VERIFIED
VERIFIED AS DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.