not that this will solve your problem, it may help you fix it.
http://www-106.ibm.com/developerworks/xml/library/x-xslt2/index.html?open&l=
bigx-2,t=gr,p=x.saxon
I know that we used to cache the parsed XSL sheet, this way we increased our
performance dramatically, otherwise, the XSLT parser has to parse the XSL
everytime you use it.
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Sent: Wednesday, April 18, 2001 7:55 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Not so much JBoss, but XSL/XSLT
We have run it under Optimize It and the objects appear to be cleaning up
properly - in fact, the profiling tool showed us that there was a HUGE
number
of objects being used just to do a single transformation (as per the XSLT
implementation)!!
We've thought about the idea of clustering more, smaller sized VM's, but
figured that would take a bit more programming to pull off. We had tried
running a test case in multiple VM's, but that didn't help too much because
the added overhead of the additional VM's killed us (which may be due to
how we had tuned the vm settings.)
Anyways, back to the drawing board...
Robert
Robert Schulz <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/17/2001 07:22 PM
Please respond to jboss-user
To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
cc:
Subject: RE: [JBoss-user] Not so much JBoss, but XSL/XSLT
Don't know about XSL but this sounds like a VM garbage collection problem.
What seems to happen with large heap sizes is that it keeps allocating
without
collecting and then gets tangled up when trying to collect ... try
clustering over
a number of smaller heap size virtual machines. Also, use some profileing
tool
(optimize it) to see what's happening and whether you are hanging on to no
longer
needed objects.
R.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 18 April 2001 8:29
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Not so much JBoss, but XSL/XSLT
Sorry to post this here, but I know more eyes will see it.
We've looked at a number of different XSL/XSLT Processors
and found one that is documented fairly well, runs fast, but
apparently doesn't scale very well.
For example, at up to loads of about 300 users it performs
very well. But, go beyond that, say to 500 users and it just
crawls like a dog - running on a 4-CPU (700MHz each) box
with 4G ram!! The cpus are running at about 80% capacity
and our memory usage is over 1G (for whatever reason, we
can't set the heap size any larger than that).
So - anyone have any experiences with XSL transformations
and scalability??
I'd love to know.....
Robert
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
