I basically want to now how much better performance I can get by using for exampel XML::XSLT
Who says it will be faster;) Although I'm biased towards doing things the XML way, i.e. use XSLT to transform a XML document, I sometimes encounter performance issues with XSLT. How complex is the resultset and what is the kind transformation your aiming for? The 78kb doesn't sound to scary to me. I suppose you can also limit the size of the resultset, much like you can limit the returned number of rows for a mySQL query? I wonder why mySQL was the bottleneck and what product you use now. Please provide some more info and maybe an example of a (representative) resultset and the kind of transformation you want to do.
Cheers
Harry
In reply to Re: XSL transformation vs. parsing of html - Performance benefits
by dHarry
in thread XSL transformation vs. parsing of html - Performance benefits
by DreamT
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |