Re: XML/XSLT processing times

>>>>> "Colin" == Colin Paul Adams <[email protected]> writes:

    Colin> I did some timings of other methods of copying an XML file to
    Colin> try to put this into perspective:

You could try the expat one, this was one of my reasons for using expat
as expat was still faster, despite the prohibitive event chaining
overhead. It's an interesting architecture, but performance is ****.

Did you look at memory consumption as well? That's also a biggie with
Eiffel. If you don't use memory, like the C versions do, performance is
much better.


    Colin> Anyway, there seems little hope of getting the XSLT library
    Colin> to perform on this basis. It would seem the entire XML
    Colin> parser/event infrastructure would need re-writing. I have no
    Colin> appetite for the task given the current W3C climate.

If you need performance, absolutely. As we can now use agents, we
probably can cleanup this a bit, and have the event infrastructure sit
on top of that.

BTW, I've always found the ISE profiler an indispensable tool in solving
performance problems, but as you say, it'll be a lot of work.

-- 
Cheers,

Berend de Boer

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/