Closed
Bug 7189
Opened 25 years ago
Closed 25 years ago
Speed up RDF initialization
Categories
(Core Graveyard :: RDF, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
M9
People
(Reporter: leger, Assigned: dp)
Details
(Whiteboard: [Perf])
TO DO for Performance: When the code to initialize RDF gets hit. It seems to take quite a while. Is there anything we can do to speed up RDF initialization?
Comment 1•25 years ago
|
||
How do we know that this is the case? Is there a Quantify trace around that indicates this?
i'd give you one if i knew how to run quantify. it's on my list of things to figure out... (is there some tutorial out there i can look at?)
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M7 → M8
Comment 4•25 years ago
|
||
Moving to M8, when DP and I plan to do some focused startup performance analysis.
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Comment 5•25 years ago
|
||
Clobbering this bug. No specifics. Not useful.
Let's not "bag the bug" because we don't have enough for you yet. waterson, I'll assign to me while I get you some quantify data, then throw back over to you...
Comment 8•25 years ago
|
||
I think it _is_ bogus to re-open this as a bug. We have _no evidence_ that "RDF initialization" is a bottleneck. How do I know that? Well, there is no such thing as "RDF initialization". So this is sort of like sending somebody out to hunt for snipe. :)
This bug was given to me by jevering...jevering, do you want to mark this Invalid?
Updated•25 years ago
|
Target Milestone: M8 → M9
Comment 10•25 years ago
|
||
waterson, if RDF doesn't get initialized how does it run? ;-) -snipe hunter's anonymous
Comment 11•25 years ago
|
||
My point is, there is no "globally initialize RDF now" routine that gets called. Each _individual_ datasource does initialization when it gets created. The RDF service creates some hashtables when it's created (but that's about it).
Updated•25 years ago
|
Assignee: jevering → dp
Comment 12•25 years ago
|
||
moving over to dp. if dp can find something here lets reassign to waterson, otherwise lets close this.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
Comment 13•25 years ago
|
||
We have done sufficient performance analysis to rule this one out now. The problems are more registry related at this point.. closing out. This may have been filed without fully understanding the problem (yes, from my report).
Comment 14•25 years ago
|
||
marking verified per jevering's comments.
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•