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?

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?)

Moving to M8, when DP and I plan to do some focused startup performance analysis.

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...

Clearing Invalid...phillip come see me regarding quantify

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?

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).

moving over to dp. if dp can find something here lets reassign to waterson, otherwise lets close this.

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).

marking verified per jevering's comments.