Bruno Haible <br...@clisp.org> writes:
> Can you please
> * measure the execution time of each of the locking tests?
Sure. Let me know if there is any other tests you need run.
> test-pthread-mutex
$ time ./gltests/test-pthread-mutex
Starting test_pthread_mutex_normal ... OK
Starting test_pthread_mutex_recursive ... OK
real 0m0.873s
user 0m1.282s
sys 0m4.278s
> test-pthread-rwlock
$ time ./gltests/test-pthread-rwlock
Starting test_rwlock ... OK
real 0m6.091s
user 0m0.423s
sys 0m7.351s
> test-lock
$ time ./gltests/test-lock
Starting test_lock ... OK
Starting test_rwlock ... OK
Starting test_recursive_lock ... OK
Starting test_once ...Alarm clock
real 10m3.724s
user 70m3.914s
sys 9m39.292s
Here is the output of sysstat(1) from another ssh session:
/0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /10
Load Average 11.0|||||||||||||||||||||||||||||||||||||||||||||
/0 /10 /20 /30 /40 /50 /60 /70 /80 /90 /100
collin 23352 test-lock XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> test-rwlock1
$ time ./gltests/test-rwlock1
real 0m0.215s
user 0m0.001s
sys 0m0.001s
> test-mtx
$ time ./gltests/test-mtx
Starting test_mtx_plain ... OK
Starting test_mtx_recursive ... OK
real 0m0.920s
user 0m1.377s
sys 0m4.201s
> * tell how many threads your machine supports?
I created the virtual machine with 8 cores and 8 GB memory.
> * report the result of the configure test
> checking whether pthread_rwlock_rdlock prefers a writer to a reader... ?
My configure says:
checking whether pthread_rwlock_rdlock prefers a writer to a reader... yes
>> [1] https://lists.gnu.org/archive/html/bug-findutils/2024-06/msg00048.html
>
> That seems unrelated.
Sorry. I just meant to show that it was recent. That is when I
encountered it. The message wasn't related.
Collin
