wording

Author: gaultier

detect_data_races_with_dtrace.html

@@ -661,7 +661,7 @@ <h2 id="benchmarks">
 </ul>
 <p>Commentary:</p>
 <ul>
-<li>When there are races, DTrace performs really badly because it reports all races it sees, which is however great for the DevUX. If we make DTrace also report timestamps and the call stack, the runtime goes to 7.5s.</li>
+<li>When there are races, DTrace performs really badly because it reports all races it sees, which is however great for the developer experience. If we make DTrace also report timestamps and the call stack, the runtime goes to 7.5s.</li>
 <li>DTrace has many tunables so it's possible that we can make it much faster this way.</li>
 <li>The racy program in release mode never terminates because as previously mentioned, the compiler does whatever it wants in the presence of undefined behavior, and in this case, generates an infinite loop.</li>
 <li>In the absence of data races, DTrace performs really well compared to TSan, we only see a ~3-4x slowdown, compared to a 16x slowdown with TSan. This of course depends on how many probes fire, and how much our script prints.</li>

detect_data_races_with_dtrace.md

@@ -505,7 +505,7 @@ How the benchmarks were done:
 
 Commentary:
 
-- When there are races, DTrace performs really badly because it reports all races it sees, which is however great for the DevUX. If we make DTrace also report timestamps and the call stack, the runtime goes to 7.5s.
+- When there are races, DTrace performs really badly because it reports all races it sees, which is however great for the developer experience. If we make DTrace also report timestamps and the call stack, the runtime goes to 7.5s.
 - DTrace has many tunables so it's possible that we can make it much faster this way.
 - The racy program in release mode never terminates because as previously mentioned, the compiler does whatever it wants in the presence of undefined behavior, and in this case, generates an infinite loop.
 - In the absence of data races, DTrace performs really well compared to TSan, we only see a ~3-4x slowdown, compared to a 16x slowdown with TSan. This of course depends on how many probes fire, and how much our script prints.

feed.xml

@@ -2,7 +2,7 @@
 <feed xmlns="http://www.w3.org/2005/Atom">
 <title>Philippe Gaultier's blog</title>
 <link href="https://gaultier.github.io/blog"/>
-<updated>2026-03-19T08:30:52+01:00</updated>
+<updated>2026-03-19T08:37:08+01:00</updated>
 <author>
   <name>Philippe Gaultier</name>
 </author>
@@ -397,7 +397,7 @@
 <title>Detect data races with DTrace in any language</title>
 <link href="https://gaultier.github.io/blog/detect_data_races_with_dtrace.html"/>
 <id>urn:uuid:413e821b-8449-5c1c-85d6-578aa3fe3f74</id>
-<updated>2026-03-19T08:30:52+01:00</updated>
+<updated>2026-03-19T08:37:08+01:00</updated>
 <published>2026-03-11T13:35:11+01:00</published>
 </entry>
     </feed>