|
From: Bart V. A. <bar...@gm...> - 2006-08-24 12:38:02
|
Hello, I ran the following tests: (1) time bash -c 'for ((i=0;i<5000;i++)); do echo n "$i "; done' (2) valgrind --trace-children=yes time bash -c 'for ((i=0;i<5000;i++)); do echo n "$i "; done' on the following two platforms: (1) OpenSuSE 10.1 running on VMWare on a 2.8 GHz Pentium IV CPU, with Valgrind 3.1.1 (V installed locally) (2) MontaVista Linux Professional 4.0.1 running on a 800 MHz PowerPC 440GX CPU, with Valgrind 3.2.0 (V started over NFS) Resulting execution times on the x86 platform: 1.06s for test (1) and 16.6sfor test (2), or a slowdown of about 16 times. Resulting execution times on the ppc32 platform: 1.8s for test (1) and 400s for test (2), or a slowdown of about 222 times. Why is the slowdown of Valgrind on the ppc32 platform I tested so much larger (more than ten times !) than on the x86 platform ? Should I do more tests -- e.g. with another Valgrind version ? |