Dr. Tapaal,
An often heard suggestion regarding performance is: Just test it.
It seems hard to me to send useful pointers based on this little information
and without any knowledge what the "complex algorithm" does and how the XSLT is
called ("each invocation of").
But, I would be very interested in your observations regarding the performance
calling a Java class over and over again (seemingly). Maybe you can share the
results of your tests and observations?
Thanks,
- Michael
Am 04.06.2016 um 00:16 schrieb Mailing Lists Mail
daktapaal(_at_)gmail(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>:
Dear All,
we are having the following situation..
We are working with the some Stock Market Data where some of the
values we need are done by a complex algorithm that is written in Java
, typically for the forcast etc. The XSLTs are all compiled .. We
instantiate the object within the XSLT using the new() and then call
the Java methods of that object, which returns some statistical
information.
Which one of the assumptions are correct? I believe the assumption1
to be true but checking ..
Scenario :
I am using the XSLT on Trillions of Nodes .My situation demands that I
treat each Node individually and run the XSLT on each of these nodes
separately. This means these nodes will be diced first and then , the
XSLT will be called on them
Assumption1
==========
there will be trillion objects created, with each invocation of the
XSLT. and the XSLTs being compiled has nothing to do with the Object
creation, as the objects will be created at run time?
Assumption2
==========
Since I have precompiled the XSLTs, it should not create trillions of
java objects
Any pointers please>
Dr.Tapaal
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--