Closed Bug 67134 Opened 24 years ago Closed 20 years ago

perf: multiple mark as read (not mark all read) is slow

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 227011
mozilla1.0.1

People

(Reporter: sspitzer, Assigned: sspitzer)

References

Details

(Keywords: perf)

for local folder, we call the our folderListener's OnItemIntPropertyChanged()
once per message to update the TotalUnreadMessages.

we should be batching them.

note, mark all read performance is much better.
Keywords: perf
QA Contact: esther → stephend
Hardware: PC → All
accept, 0.9
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
marking nsbeta1+. I don't think this gets fixed by the rewrite, but if it doesn
that would be great.
Keywords: nsbeta1
Whiteboard: [nsbeta1+]
Priority: -- → P3
moving to mozilla0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
moving to 0.9.2
Target Milestone: mozilla0.9.1 → mozilla0.9.2
moving to 0.9.3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
moving to 0.9.4
Target Milestone: mozilla0.9.3 → mozilla0.9.4
slide to 0.9.5

Target Milestone: mozilla0.9.4 → mozilla0.9.5
this has gotten better, but more work might need to be done.  (like batching).

moving out.
Target Milestone: mozilla0.9.5 → mozilla0.9.7
Blocks: 104166
Keywords: nsbeta1-
Whiteboard: [nsbeta1+]
Target Milestone: mozilla0.9.7 → mozilla1.0.1
[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021114]

Marking as read a group of 1100 messages took close to a minute. Is this bug
dead ? Target is 1.0.1
Netscape 7.0.1 doesn't seem to exhibit this behavior as much on a P4-1.6 with
384 megs ram laptop.  Mozilla 1.2.1 (and 1.2, but I don't believe that 1.2beta
did) seems to thrash the harddrive as it does the "select about half of the
messages, then hit 'm' to mark as read", and takes longer than 5 minutes (my
'give up' time) to complete the operation.  Netscape 7.0.1 takes 45-50 seconds
to do the same task.

Additionally, moving ~1000 messages from one folder to another in Mozilla 1.2.1
takes far too long (more than 5 minutes, accompanied with constant thrashing of
harddrive, but no apparent change in total memory footprint (about 22 MB in
memory, and VM size lists 35 MB for whole operation).  CPU isn't particularly
taxed (5% on average), but everything is slow as harddrive thrashing
continually. Total memory usage not increasing much at all.

Doing the "CTRL-SHIFT-C" operation (mark all as read) on a folder with 1000
messages in Netscape 7.0.1 almost instantaneous (less than 3 seconds).  In
mozilla 1.2.1, approximately 1 minute 54 seconds (second hand on watch timed).

All of this on a PC running Windows XP Home. This behavior is only observed on
the laptop.  My 900 MHz athlon with 256 megabytes memory does NOT exhibit this
situation (though it is running Linux).  This behavior seems to have started
after updating mozilla to 1.2.1 from 1.2Beta.
this is slow because we're doing a flush/sync after every mark read instead of
after the whole operation is finished
David Bienvenu:
Did bug 227011 fix this? I don't know if attachment 136503 [details] [diff] [review] of that bug
implements what you suggested in comment #11.
yes, thx, I'll mark this as a dup.

*** This bug has been marked as a duplicate of 227011 ***
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.