Closed
Bug 8822
Opened 27 years ago
Closed 27 years ago
Performance improvement of collation key generation in messenger
Categories
(MailNews Core :: Database, defect, P3)
MailNews Core
Database
Tracking
(Not tracked)
VERIFIED
FIXED
M12
People
(Reporter: nhottanscp, Assigned: Bienvenu)
References
Details
(Whiteboard: [Perf])
There is a performance issue of generating collation keys for message sort. The
current code instanciates locale and collation per key bases. This is not
efficient as there are XPCOM overhead involved. Only one collation instance
should be generated per locale (i.e. per mail folder) then keys to be generated
using that instance.
nsMsgDatabase.cpp
nsMsgDatabase::RowCellColumnToCollationKey
|
||
Updated•27 years ago
|
Assignee: phil → bienvenu
|
|
||
Comment 1•27 years ago
|
||
Reassign to bienvenu
|
|
Assignee | |
Updated•27 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M12
|
|
Assignee | |
Updated•27 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 27 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 2•27 years ago
|
||
fixed in nsMsgDatabase.h, cpp, on the necko branch - added method
GetCollationKeyGenerator() .
QA has no resources to verify this bug. Please verify it or advise us how to do
it. thanks.
|
|
Assignee | |
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
|
||
Updated•21 years ago
|
Product: MailNews → Core
|
||
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•