Ok, after doing more detailed timing tests, I find that Xalan is not the problem. I have some code that translates SOAP nodes to DOM nodes (we're forced to use the ancient version of JWSDP where the SOAP node classes don't inherit from the DOM node classes, so we have to manually translate them). In my test case on Solaris, with the default Xerces, I see average times of ~90ms. With the Xerces that comes with Xalan 2.7.0, this balloons up to ~370ms. Again, I didn't see this discrepancy when I ran it on Windows. I'll break down the timing of that code in more detail, but it looks like it doesn't have anything directly to do with Xalan.
> -----Original Message----- > From: Brian Minchau [mailto:[EMAIL PROTECTED] > Sent: Friday, March 24, 2006 3:28 PM > To: Karr, David > Cc: [email protected] > Subject: Re: Strange performance degradation upgrading from > xalan-j 2.4.1 to 2.7.0 on Solaris > > > David, > Nice that it ran faster on your laptop. Too bad about the > Solaris 8 box. Makes me think of some sort of synchronization issue. > > Can you tell me more about your testcase? > > > - Brian > - - - - - - - - - - - - - - - - - - - - > Brian Minchau > XSLT Development, IBM Toronto > e-mail: [EMAIL PROTECTED] > > > > > > > "Karr, David" > > <[EMAIL PROTECTED] > > net> > To > > <[email protected]> > 03/24/2006 05:58 > cc > PM > > > Subject > Strange performance > degradation > upgrading from xalan-j > 2.4.1 to > 2.7.0 on Solaris > > > > > > > > > > > > > > > > > > I built a test case with an xslt in my messaging bus. I > tested it on my laptop with both Xalan-J 2.4.1 and Xalan-J > 2.7.0 (although that was a while ago). I found that Xalan-J > 2.7.0 improved performance a little bit. I then copied the > same test case to a Solaris 8 box. I found that the test > case with Xalan-J 2.7.0 took TWICE as long than with Xalan-J > 2.4.1. I tried it several times, with the same results (in > each version). I'm toggling between the two Xalan versions > by using the "endorsed" directory of the JRE. I put the > xalan.jar, xml-apis.jar, xercesImpl.jar, and serializer.jar > from Xalan-J 2.7.0 into the endorsed directory, and I rename > the directory when I test it with version 2.4.1. > > My test case is running 1000 of the same transformation, > synchronously on the same thread. I'm using a cached > Templates object to get the Transformer object from. > > Is there something simple that could be causing this unusual > performance degradation in version 2.7.0? > > >
