[Mono-list] Extremely poor performance of ODFConverter/Mono on Linux vs Windows .Net

[Atsushi Eno]

As long as the license permits, you might want to try to switch to 
saxon.net, which is XSLT 2.0
implementation but for 1.0. (saxon is under MPL.)

Atsushi Eno

On 2009/10/16 17:38, Michael Meeks wrote:
> Hi Roman,
>
> On Thu, 2009-10-15 at 07:02 -0700, RomanP wrote:
>    
>> I checked the performance of ODFConverter application for DOCX ->  ODT
>> conversion (http://sourceforge.net/projects/odf-converter)
>>      
> 	The other issue here - around optimisation is - why bother ? there are
> some examples of horrific performance on Windows / .Net too, of the
> order of hours to open some larger files ;-) so - at least the OO.o
> team's focus has been to work on native filters built into OO.o instead.
>
> 	Of course, it is interesting that when used with some staggeringly
> large and highly complicated [ try debugging or profiling them ] XSLT
> scripts Mono performs much worse than .Net - but, this seems to be to be
> a corner case of little real interest - beyond the (rather ill-advised)
> use of XSLT in the odf-converter ;-)
>
> 	At least that is my take. Worse than that, last I looked it was rather
> hard to determine what is poor performance of the XSLT itself [ using
> poor constructs that chew CPU ], and what is a sub-optimal
> implementation in the XSLT interpreter. But if you have time to sink
> into this - I don't think people would complain to get the patches ;-)
>
> 	Regards,
>
> 		Michael.
>
>