optimize SetReferences() / ParseReferences()

VERIFIED FIXED in mozilla0.9.6

Status

MailNews Core
Backend
VERIFIED FIXED
17 years ago
10 years ago

People

(Reporter: (not reading, please use seth@sspitzer.org instead), Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

({perf})

Trunk
mozilla0.9.6

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

optimize ParseReferences()

patch coming.

Comment 2

17 years ago
Comment on attachment 53357 [details] [diff] [review]
patch

rs=bienvenu
Attachment #53357 - Flags: superreview+
Status: NEW → ASSIGNED
Summary: optimize ParseReferences() → optimize SetReferences() / ParseReferences()
Target Milestone: --- → mozilla0.9.6
fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
Keywords: perf
QA Contact: esther → stephend
Hardware: PC → All
Folder Loading Speed:

10-5-2001 trunk:

1.67 (2.12 1.42 1.46)

10-15-2001 trunk:

1.56 (1.56 1.55 1.52)

Cavin I think has finished logging the API time of what we do parsing the folders 
locally.  Perhaps that's a better way of measuring folder loading speed, since 
even with the perf stuff that you've landed, Seth, my numbers don't reflect 
anything (in fact, they go up ever so slightly, as they do to normal 
fluctuation).

But anyway, I'm sure under the actual API by itself (without calling layout, 
etc.) this fix helped.

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.