I just noticed a bug in my testbed/benchmarking code. It's fixed, but I decided to compare version 6 of the code against the *unsafe* decompressor again. The results of the three runs I've put it through after changing it to compare against the unsafe decompressor were startling. `Tiny's` compressor is still faster - I've seen it be rated up to 3% faster. The decompressor, OTOH, when compared to the unsafe version (which is the comparison that started me on this binge of hacking), is more than 7% worse. About 11% slower on the original test against a C source file, and about 6% slower for random data. However, looking at the numbers involved, I can't see a reason to keep the unsafe version around - the percentages look worse than they are - from 1 to 3 microseconds. (well, the compressed-cache people might want those extra usecs - but the difference will never be noticeable anywhere outside the kernel) DRH
Attachment:
lzo1x-test-6a.tar.bz2
Description: application/tbz
- Follow-Ups:
- Re: [RFC] LZO de/compression support - take 6
- From: "Nitin Gupta" <[email protected]>
- Re: [RFC] LZO de/compression support - take 6
- References:
- [RFC] LZO de/compression support - take 6
- From: "Nitin Gupta" <[email protected]>
- Re: [RFC] LZO de/compression support - take 6
- From: "Bret Towe" <[email protected]>
- Re: [RFC] LZO de/compression support - take 6
- From: "Nitin Gupta" <[email protected]>
- [RFC] LZO de/compression support - take 6
- Prev by Date: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM hook
- Next by Date: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- Previous by thread: Re: [RFC] LZO de/compression support - take 6
- Next by thread: Re: [RFC] LZO de/compression support - take 6
- Index(es):