Closed Bug 30961 Opened 25 years ago Closed 24 years ago

Mark all read is too slow, no progress indication

Categories

(MailNews Core :: Backend, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 17470

People

(Reporter: rzach, Assigned: scottputterman)

Details

(Keywords: perf)

Marking all messages read in News using Message | Mark > All Read is way too slow. Marking all messages of n.p.m.unix (about 3800) read on Mozilla took 60 seconds, on NS 4.7 it took about 4. Furthermore, marking all read needs to be asynchronous, so the app doesn't lock up during the operation like it does now, and there is no progress indication (in NS 4.7, the status bar indixates "marked xxx messages read"). Linux build 2000.03.07.09
Keywords: perf
This should go to the other scott, I think.
Assignee: mscott → putterman
QA Contact: lchiang → suresh
Also see bug #18515
Status: NEW → ASSIGNED
Target Milestone: --- → M18
pratikd - can you update with the last linux test results in this bug?
QA Contact: suresh → pratikd
"Mark All Read" seems to be really slow compared to NS 4.7. Last comm linux build tested for Performance was 2000-06-29-08. It took on average 38.4 seconds to "mark as read" approx 500 news messages. Std. Dev. = 0.59. NS 4.7 takes about 2.52 seconds on average to do the same.
nominating for nsbeta3
Keywords: nsbeta3
Isn't this a dup of 17470, which I've assigned to Hyatt?
yep *** This bug has been marked as a duplicate of 17470 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.