On Tuesday 30 August 2011 16:19:24 Cristian Rodríguez wrote:
On 30/08/11 05:58, Ruediger Meier wrote:
On Tuesday 30 August 2011, Claudio Freire wrote:
BTW you can see that user time is 15% higher with pigz so compression per core cycle is worse.
That's called cache pressure. It happens when more than one process is running. Run four gzips concurrently, you'll probably experience the same increase.
Yes, ... ... and ouf course you will see that gzip has more throughput in any case while the system is less on load:
# 4 x gzip in parallel rudi@quant:/tmp> time ( for i in `seq 1 4` ; do gzip -c hist.csv & done ;wait ) > /dev/null
real 0m30.500s user 1m59.311s sys 0m0.978s
# 4 x pigz in parallel in parallel rudi@quant:/tmp> time ( for i in `seq 1 4` ; do ~rudi/tmp/pigz-2.1.6/pigz -c hist.csv & done ;wait ) > /dev/null
real 0m35.164s user 2m18.944s sys 0m1.236s
# 4 x pigz sequential -bash: syntax error near unexpected token `)' rudi@quant:/tmp> time ( for i in `seq 1 4` ; do ~rudi/tmp/pigz-2.1.6/pigz -c hist.csv ;done ;wait ) > /dev/null
real 0m35.147s user 2m16.647s sys 0m3.398s
is /tmp and in ram ? otherwise your "tests" are meaningless, because you are then measuring I/O aka. the wrong thing!
One thing that bugs me with this Is this going to be a choice thing ie you can continue to use the original and fully working stuff or choose to install the dodgy unknown and hope it works if you are going to have a choice carry on if you are not the not a hope in hell Pete . -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.10-0.2-desktop KDE Development Platform: 4.6.00 (4.6.0) 17:20 up 4 days 17:06, 4 users, load average: 0.12, 0.15, 0.10 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org