XOM API for Processing XML with Java

[Janek Bogucki <janekdb AT yahoo.co.uk>]

I performed a benchmark on the class loading times for a compressed jar 
versus an uncompressed jar
and my conclusion was that there is not much justification for distributing 
xom-1.0d25.jar in
uncompressed form. (I am assuming class loading time improvement was the 
motivation for generating
an uncompressed jar. If that was not the sole reason then this may be 
irrelevant.)

Jar sizes:

    99590 xom-1.0d25-compressed.jar
   248217 xom-1.0d25.jar

The benchmark class is attached. This is the result of five runs. Times in 
milliseconds.

   uncompressed    compressed
   417             439
   428             440
   414             434
   415             441
   416             445

Given that a class is loaded once, on demand, in the lifetime of the JVM this 
benchmark shows a
marginal gain in a usage pattern designed to maximise the difference. 
Shipping a jar which is ~2.5
times as large as the compressed version is the wrong size of 80/20. Changing 
build.xml to
generate a compressed jar would definitely improve XOM's golf score.

-Janek


        
        
                
___________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html