Closed Bug 95825 Opened 24 years ago Closed 9 years ago

cache sort result of charset menu

Categories

(Core :: Internationalization, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ftang, Assigned: smontagu)

References

Details

(Keywords: perf)

currently, we use nsICollation at the start up time to build the charset menu. The delay of building charset menu is report in a different bug. But we should also consider cache the sort result in a disk cache (nsIPref*?) so we don't need to sort again and again.
the other thing we should consider is if the list is static per localization, we should presort in the localization time and remove the sorting in the run=time.
Keywords: perf
Marking as blocker of bug 7251 (start-up time).
Blocks: 7251
mark m94
Target Milestone: --- → mozilla0.9.4
changing to m0.9.5
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.4 → mozilla0.9.5
assigning to jbetak
Assignee: yokoyama → jbetak
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9.5 → ---
Blocks: 103175
marking 1.0, I'm quite confident I can complete the work on lazy charset menu initialization, this bug would be an addional optimization, which needs to be re-evaluated at a later time. I might be able to resolve it as part of my patch for bug 64146.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
jbetak's contract is up. Bulk move bugs to ftang
Assignee: jbetak → ftang
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Keywords: mozilla1.0
Target Milestone: mozilla1.0 → Future
Changing QA contact to bobj for now. Bob, please re-assign further as you see is appropriate.
QA Contact: andreasb → bobj
-> to default owner (rather than ftang's WONTFIX)
Assignee: ftang → smontagu
Status: ASSIGNED → NEW
QA Contact: bobj → amyy
Target Milestone: Future → ---
QA Contact: amyy → i18n
Current in-RAM caching of the sorted menu is fast enough.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.