Dear Michael
Thanks a lot for your support.
> If it turns out that saxon:evaluate is a significant contributor (and the
> way to determine that is to do a control run that's identical except for
> the
> use of saxon:evaluate), then the obvious way to improve things is by
> caching. You can split saxon:evaluate into two phases, saxon:expression
> which parses the expression and saxon:eval which evaluates it. The
> expensive
> phase is the first one, and you need to organize your application so each
> expression is only compiled once, and then cached.
In order to compare the performance between saxon:evaluate and saxon:eval I
have extended my XSLT script. Producing the exact the same result the
performance looks like follows:
saxon:evaluate)
 needed 3317 ms in the average to TRAX the 120 calls
saxon:eval)
 needed 134 ms in the average to TRAX the 120 calls
Principally the performance of saxon:eval seems to be IO. But saxon:eval
does not give me the possibility to be generic. My question is now, would it
be possible to cache the saxon:evaluate expressions.
Salve,
Raffaele
