On Fri, 1 Feb 2002, [EMAIL PROTECTED] wrote: > hello > I am totally new to axkit. > lets say, I have 25 web servers for customers > all pages are generated dynamically. we want to switch > to something with XML/XSLT. > > the xml files will come dynamically out from some middleware > then I have XSLT stylesheets which transfrom the XML files > into html. > the performance bottleneck of this is the XSLT transformation. > one idea is to write an apache module which handles the transformation in C. > this is obviously very fast, but also very ugly to write and to maintain. > > it should also be possible to write XSTL extensions. > > now my question. > can this be done also with axkit??
Sure. > how fast do you think would be an axkit solution compared to the apache > xslt module (using libxslt from xmlsoft.org)? How fast do you want it to be? Seriously - there a zillion different ways of architecting an AxKit site. Just ask Mike Chamberlain for example - he doesn't cache any output, but still gets good performance because he's put a lot of work into the backend. There are lots of issues at hand. For example does your C module cache stylesheets between requests? (AxKit does). > in the end we will have more than 30 web servers with very, very high traffic. One thing to consider on a high traffic site is AxKit gzip encoding stuff. Makes a huge difference if you can cache it. > axkit seems to be great and I really would like to know if this is an > option here. but I am sure that some will argue due to the fact that some > of axkit is written in perl, it will be very slow. > so I need some arguments against this. Take a look at the code. Really - load up AxKit.pm in an editor. On a high performance setup, you'll go from fast_handler (8 lines of code to execute), to main_handler (14 lines of code to execute) before you get to the cache delivery. Now there's some bits of code underneath all that, and some stat calls (which you can turn off with AxDependencyChecks Off) and some C code executed, but in all it's very little code. If you're not caching, it's a little bit more code to get to the pipeline execution (process_request()), but not a whole lot, and the XSLT stuff is all C. It may not be fast enough - only testing can tell you that. All I can say is its fast enough for some fairly high traffic sites, and if there are slow areas I'll just convert them to C and be done with it ;-) -- <!-- Matt --> <:->Get a smart net</:-> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
