Closed Bug 114700 Opened 24 years ago Closed 24 years ago

Remove PR_Sleep(PR_MicrosecondsToInterval(500UL))in nsMailboxProtocol.cpp

Categories

(MailNews Core :: Backend, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: naving, Assigned: naving)

Details

(Keywords: perf)

Attachments

(1 file)

I have just tried commenting it in my tree and batch deleting/copying local mail works ok. Looks like the necko guys have fixed this problem that was there. Is there any special case you want me to check?
This sleep call is on nsMailboxProtocol.cpp:325
Keywords: perf
oh boy, tha's a can of worms you want to open. You need to try copying large numbers of different sized messages between folders, with various sorts, etc. I can try it if you want.
I have just tried copying message of size in range 1KB < size <= 2MB and it works ok. I don't know how sorting would play a role here.
I assume you mean multiple messages, not single messages of sizes varying from 1K to 1MB (the code in question is only executed when you copy/move multiple messages). The problem only occured when you copied multiple messages, a large number of messages, of varying sizes. I tried reproducing the problem, and couldn't, after commenting out that line, so if you want to live dangerously, r=bienvenu
ya, i did multiple messages. i believe this will speed up batch deleting a lot. i will try some more cases. I will back it out if it doesn't give us much gains.
We're talking about a 1/2 millisecond (less than 1/thousandth of a second) gain per message, so we know pretty much what the improvement will be. It's great if we can remove this since it was an ugly hack anyway. Your previous fix for multiple local message move/copy might have also fixed the problem this silly hack was put in for in the first place.
Attached patch proposed fixSplinter Review
tested varying size of messages in the batch deletes. worked ok. I am hoping for some indirect gains.
QA Contact: esther → stephend
Is this worth taking? It sounds like the performance gain isn't going to be noticeable. Did we determine that it's not risky to take this out?
Status: NEW → ASSIGNED
I think we should take it - I thought we'd checked this in a long time ago :-).
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Performance results for local folder batch delete/copy operations: 2002-01-04 Win32 build: 17.02 seconds to Delete 2001 msgs 24.35 seconds to Copy 2001 msgs 2002-01-07 Win32 build: 15.64 seconds to Delete 2001 msgs 23.78 seconds to Copy 2001 msgs. A side note, between the 4th and the 7th build, something broke our 'Copying xxx of xxx messages to Sent' and 'Deleting xxx of xxx messages' notifications. Anybody know if that's filed already or not? Verified FIXED with the build mentioned above.
Status: RESOLVED → VERIFIED
OS: Windows NT → All
Hardware: PC → All
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: