Re: tsan execution time for 2 threads over 1

7 views
Skip to first unread message

Dmitry Vyukov

unread,
Apr 5, 2013, 1:03:14 AM4/5/13
to thread-s...@googlegroups.com
Yes, this is expected because Valgrind is single-threaded, so it can't take any advantage of threads/cores.

Valgrind-based TSan is deprecated in favor of new compiler-based TSan:
The new TSan works with gcc or llvm compiler and is fully parallel.



On Thu, Apr 4, 2013 at 6:10 PM, Marco Paniconi <mar...@google.com> wrote:
Hi,

   I'm running an encoder test with tsan, and the execution time
   of the test is ~1.6 times longer when the codec is using with 2 threads vs 1.
   Is the longer execution time expected if the codec is using multi-threads for encoding?
   Also, what does 2 bug_57266c/68 bug_57266a mean in the 2-thread case output?
thanks,

// FOR 1 THREAD encoding //

09:45:10 common.py [INFO] process ended, did not time out
09:45:10 common.py [INFO] flushing stdout
09:45:10 common.py [INFO] collecting result code
-----------------------------------------------------
Suppressions used:
  count name
      1 bug_103711a
-----------------------------------------------------
09:45:10 tsan_analyze.py [INFO] PASS: No reports found
09:45:10 valgrind_test.py [INFO] Test execution completed successfully.
09:45:10 valgrind_test.py [INFO] Analysis completed successfully.
09:45:10 valgrind_test.py [INFO] elapsed time: 00:15:24


// FOR 2 THREAD encoding //

10:13:53 common.py [INFO] process ended, did not time out
10:13:53 common.py [INFO] flushing stdout
10:13:53 common.py [INFO] collecting result code
-----------------------------------------------------
Suppressions used:
  count name
      1 bug_103711a
      2 bug_57266c
     68 bug_57266a
-----------------------------------------------------
10:13:53 tsan_analyze.py [INFO] PASS: No reports found
10:13:53 valgrind_test.py [INFO] Test execution completed successfully.
10:13:53 valgrind_test.py [INFO] Analysis completed successfully.
10:13:53 valgrind_test.py [INFO] elapsed time: 00:25:06

--
You received this message because you are subscribed to the Google Groups "thread-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thread-sanitiz...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply all
Reply to author
Forward
0 new messages