Closed
Bug 3350
Opened 26 years ago
Closed 26 years ago
[RDF/XPCOM] RDF significantly slower now that it's using XPCOM repository
Categories
(Core Graveyard :: RDF, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
M9
People
(Reporter: waterson, Assigned: dp)
References
Details
(Whiteboard: [Perf])
Since Warren changed RDF resource and datasource construction to route through
the XPCOM repository, performance has slowed down significantly; e.g., it now
takes ~10sec to read in bookmarks. What's so slow about the repository?
Reporter | ||
Updated•26 years ago
|
Assignee: waterson → dp
Reporter | ||
Comment 1•26 years ago
|
||
Reassigned to dp; From his email
----
The performance problem is because ProgID to CLSID conversion now hits the
registry every time. I am changing the repository to use nsIRegistry and then
will implement the cache of progid. That should get this back on track.
----
Reporter | ||
Comment 2•26 years ago
|
||
Checked in a patch that caches ProgID-to-CLSID mappings (including misses).
This really needs to be re-worked: the code is starting to get ugly. :)
Updated•26 years ago
|
Component: Aurora/RDF BE → RDF
Product: MozillaClassic → Browser
Version: 1998-03-31 → other
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M3
Comment 3•26 years ago
|
||
is the current behavior good enough for M3? or is someone looking at this
now? lets move to M4 if performance is ok with the hack, and replace
the hack in m4.
Assignee | ||
Updated•26 years ago
|
Target Milestone: M3 → M4
Assignee | ||
Comment 4•26 years ago
|
||
Fixed multiple loads. This should improve quite a bit.
We can leave the rest for M4.
Updated•26 years ago
|
Target Milestone: M4 → M5
Updated•26 years ago
|
Target Milestone: M5 → M6
Comment 5•26 years ago
|
||
Bookmarks performance seems OK for M5. DP, could you check to make sure all
performance enhancements are completed for M6?
Assignee | ||
Updated•26 years ago
|
Target Milestone: M6 → M9
Assignee | ||
Comment 6•26 years ago
|
||
Fine tuning is what is left.
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•26 years ago
|
||
This was more of a place holder for all the performance improvements we were
planning on. They are all done.
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•