1) I'm groveling through the Xalan code, looking for performance bottlenecks, and I've noticed something a bit odd. Most of the DOM operations which get a value from a node -- getNodeName, getNodeType, etc. -- are returning in a relatively small number of ticks. JProbe reports the "line time" for these as averaging around 20-30; I think the unit is ms of CPU time.
A getNamespaceURI() call on the same node is taking significantly longer -- 141 units. A small delta, perhaps, but surprising -- and this occurs in one of Xalan's inner loops, as we generate a DTM proxy for the DOM. If anyone has an idea for why the Xerces DOM would be slower on this operation than the others, it might be worth investigating. This is with Xerces1; I haven't yet started performance testing against Xerces2, though I suppose I should. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
