This is a tad OT but as the code is copyright Axkit, I thought I'd post here.
 
 I've just started a new project and am trying to get them to change their ways 
by tidying up code etc.
 
 Anyway, they told me that for part of the site, they take XML, XML::Simple it 
and then create HTML from the resulting Perl struct.
 
 I suggested XML::LibXSLT and thought it would be quick enough to convince them 
to change.
 
 I've just done a minute test and was shocked at how slow LibXSLT is comparted 
to looping rhrough a struct creating  the HTML.
 
 I only timed the transform for LibXSLT and the whole reading of the struct.
 
 timethis( $count, sub { $html = $ss->transform( $lang_doc ) } );
 timethis 100000: 37 wallclock secs (11.46 usr +  1.21 sys = 12.67 CPU) @ 
7892.66/s (n=100000)
 
 ## reading whole struct and doing assigns to $html for the output
 timethis 100000:  5 wallclock secs ( 2.13 usr +  0.15 sys =  2.28 CPU) @ 
43859.65/s (n=100000)
 
 So, what's the point of LibXSLT when we can roll our own (despite wanthing to 
use Perl modules to make our code easier to read)
 
 -Ants
 
 
                
---------------------------------
  Yahoo! Cars NEW - sell your car and browse thousands of new and used cars 
online search now  
---------------------------------
  

Reply via email to