Closed Bug 7189 Opened 25 years ago Closed 25 years ago

Speed up RDF initialization

Categories

(Core Graveyard :: RDF, defect, P3)

Product:
Core Graveyard
Component:
RDF
Platform:
x86
Windows 95
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID

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?
Whiteboard: [Perf]
Target Milestone: M7
Blocks: 7251
How do we know that this is the case? Is there a Quantify trace around that
indicates this?
jevering or phillip, can we get a Quantify trace please?
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?)
Status: NEW → ASSIGNED
Target Milestone: M7 → M8
Moving to M8, when DP and I plan to do some focused startup performance
analysis.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Clobbering this bug. No specifics. Not useful.
Status: RESOLVED → REOPENED
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...
Resolution: INVALID → ---
Clearing Invalid...phillip come see me regarding quantify
Assignee: waterson → leger
Status: REOPENED → NEW
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. :)
Assignee: leger → jevering
This bug was given to me by jevering...jevering, do you want to mark this
Invalid?
Target Milestone: M8 → M9
waterson,  if RDF doesn't get initialized how does it run? ;-)
  -snipe hunter's anonymous
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).
Assignee: jevering → dp
moving over to dp.  if dp can find something here lets reassign
to waterson, otherwise lets close this.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
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).
Status: RESOLVED → VERIFIED
marking verified per jevering's comments.
No longer blocks: 7251
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.