![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >comp.text.xml Archive Home >Recent entries >Thread Prev - Re: Why is Intel XSLT accelerator so slow ? [Thread Next] Re: Why is Intel XSLT accelerator so slow ?To: NULL Date: 5/2/2008 10:25:00 AM >> For little XML files (under 4MB), Intel XSLT accelerator performances >> were better than Xalan performances, but for bigger files, XSLT >> accelerator starts to be _very_ slow (exponential growth of the >> processing time). Very different codebases. Probably different tradeoffs taken at all levels from data structures to algorithms. I'm not surprised that the performance curves cross each other. Reminder; XSLT, in general, requires that the whole input document be loaded into an in-memory data model since the stylesheet has full random access to it. Efficiency of that model becomes a serious issue on large docs, since swapping can be a performance-killer. See much discussion on Xylem's mailing list archives of what we've done over the years (including some "cheats" for some specific usecases), and what we've considered as possible future directions if cycles ever become available to invest in that work. | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||
|
