test-lock taking a long time?

[Simon Josefsson]

Has anyone noticed that test-lock takes a long time to complete on some
systems?  On my laptop it is fast:

address@hidden:~/src/gnutls/gl/tests master$ time ./test-lock
Starting test_lock ... OK
Starting test_rwlock ... OK
Starting test_recursive_lock ... OK
Starting test_once ... OK

real    0m1.724s
user    0m1.044s
sys     0m4.708s
address@hidden:~/src/gnutls/gl/tests master$ 

However on a otherwise idle machine with 2xE5520's (resulting in 16
virtual CPUs), it takes much longer:

address@hidden:~/gnutls-3.0.12/gl/tests$ time ./test-lock 
Starting test_lock ... OK
Starting test_rwlock ... OK
Starting test_recursive_lock ... OK
Starting test_once ... OK

real    1m49.893s
user    1m31.874s
sys     16m4.056s
address@hidden:~/gnutls-3.0.12/gl/tests$ 

Is there some scaling in the test that makes it take longer for
multi-cpu machines?  I didn't see any from a quick look.

For comparison, my laptop is running debian squeeze and the multi-CPU
machine is running Ubuntu 11.10 (i.e., libpthread is used on both
machines).

/Simon