Closed
Bug 22986
Opened 25 years ago
Closed 25 years ago
Address book sort is extremely slow
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M14
People
(Reporter: rzach, Assigned: chuang)
References
Details
(Keywords: perf)
Sorting an address book with 250 cards takes almost 30 sconds on my 400MHz K6-2
with 128MB, running RH 6.0 and Linux build 2000.01.02.09.
While sorting, the console continuously outputs
nsCollationUnix::Initialize mLocale = C
which is only output once when I do a sort in the message pane.
Sending bug to Candice for investigation. I am not sure that the problem is in
address book code, but it seems like a good place to start. cc'ing Putterman
Alec in case one of them has some insight into this.
Comment 2•25 years ago
|
||
It looks like we might be caching something in mail that is being created
multiple times in the address book? cc'ing David and Naoki.
Comment 3•25 years ago
|
||
It looks like we might be caching something in mail that is being created
multiple times in the address book? cc'ing David and Naoki.
Comment 4•25 years ago
|
||
I think the collation object needs to be cached.
In nsAbCardProperty::GetCollationKey, looks like the collation object is
generated for each collation key. We can generate the collation object once per
address book then only needs to call CreateSortKey per key generation.
Comment 5•25 years ago
|
||
yes, I agree with Naoki. The collation object should be cached.
Bulk add of "perf" to new keyword field. This will replace the [PERF] we were
using in the Status Summary field.
Comment 7•25 years ago
|
||
Wouldn't hold beta1 for this, but it would be nice to have.
Updated•25 years ago
|
Whiteboard: [perf]
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 9•25 years ago
|
||
Verified fixed on Linux build 2000.02.13.08
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•