[BusyBox] gunzip is slow

[tom at ceisystems.com]

Bastian,

	The first thing you can do is check out the CVS logs on the CVS
Web interface.  This is usually pretty helpful, as it contains the CVS
log entered by the person committing a change, and a color-coded display
of what code changed.

	The second item I would suggest is checking out what "flags" and
libraries these gunzips have been compiled with.  Sometimes these flags
(depending on the system) can make a bit of difference.  Libraries
always matter.  If you compiled busybox against uClibc and the original
gunzip against glibc, this can make a large difference also.  Keep in
mind that uClibc has been stripped down to offer good functionality and
a _large_ size decrease.  This can mean slower performance.

Good luck,
Thomas Cameron
CEI Systems, Inc.


> -----Original Message-----
> From: Bastian Blank [mailto:waldi at debian.org] 
> Sent: Saturday, April 26, 2003 7:15 AM
> To: busybox at busybox.net
> Subject: [BusyBox] gunzip is slow
> 
> 
> hi folks
> 
> i checked the time needed for unpack a gziped file with 3 different
> gunzip binaries and see that busybox cvs is the slowiest.
> 
> standard gunzip (zlib)
> $ time gunzip -c test.gz
> gunzip -c test.gz  0.12s user 0.00s system 37% cpu 0.122 total
> 
> busybox stable 0.60.5
> $ time ./busybox gunzip -c test.gz
> ./busybox gunzip -c test.gz  0.22s user 0.02s system 101% cpu 
> 0.235 total
> 
> busybox cvs 20/4/2003
> $ time ./busybox gunzip -c test.gz
> ./busybox gunzip -c test.gz  0.28s user 0.01s system 97% cpu 
> 0.296 total
> 
> are there any greater changes in the unzip algorythm between 
> stable and
> cvs?
> 
> bastian
> 
> -- 
> Pain is a thing of the mind.  The mind can be controlled.
> 		-- Spock, "Operation -- Annihilate!" stardate 3287.2
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox
>