Hi,
I was running helgrind on various medium-sized tests and I experience an
issue with helgrind's speed.
One of the tests
- runs ~3 seconds by itself
- runs ~50 seconds under memcheck (passes)
- dies after ~150 seconds completing less than 30% of work. The test
simply does not like to be delayed that much -- it has too strict timeouts.
The test has > 50 threads.
I tried profiling the helgrind run (using oprofile) and see the following
profile.
samples % image name symbol name
82533 14.9762 helgrind avl_find_node <<<<<<<<< this one
seem to have an indirect call of kCmp... Might be worth inlining
73035 13.2528 helgrind cacheline_wback
66704 12.1039 helgrind evh__mem_help_read_4 <<<< this
one seems to be called indirectly...
55637 10.0958 anon (tgid:19421 range:0x4b2f000-0x5c55000) (no symbols)
<<<< I suspect that this is the actual user's code, right?
46728 8.4791 helgrind cacheline_fetch
26357 4.7827 helgrind msm__handle_read
25291 4.5892 helgrind shadow_mem_set32
(I tested unmodified version I checked out yesterday from trunk).
What is the typical slowdown of helgrind (compared to native run or compared
to memcheck)?
Does it depend on the number of threads/locks?
Do you have any suggestions on further analysis/improvements of helgrind
performance?
Thanks,
--kcc
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
