He, hold on here Bill.
If you want to measure performance, you have to have huge testing set.
Playing with milliseconds doesn't prove anything :(
If you measure:
it doesn't prove anything. ZipInputStream could be affected by thread
scheduler and as such not active for some (e.g. 255 ms) time.
To prove something is unefficient (e.g. VFS3),
you have to create tests that will measure performance in
seconds/minutes to measurement don't be affected by thread scheduler or GC.
On 01/05/2010 06:18 PM, Bill Burke wrote:
A simple test of using ZipInputStream vs. URLClassLoader to find a
resource within jacorb.jar.
URLClasLoader is obviously using some other mechanism to find things.
JBoss, by Red Hat
Office: +420 222 365 200
Mobile: +420 731 186 942