What are the performance metrics for ThreadSanitizer?

What are the performance metrics for ThreadSanitizer?

ThreadSanitizer primarily focuses on detecting data races in C/C++ and Go programs. Key metrics include overhead, false positives, and detection latency.

How does the overhead of ThreadSanitizer compare to other tools?

ThreadSanitizer generally has higher overhead than some static analysis tools but is more effective in runtime detection of data races.

Can you explain what false positives mean in this context?

False positives occur when ThreadSanitizer reports a data race that isn't actually present, which can lead to unnecessary debugging efforts.

What can I do to reduce the overhead when using ThreadSanitizer?

To reduce overhead, you can limit the scope of the analysis, use optimized builds, or selectively enable checks for specific threads.