diff --git a/README.md b/README.md
index 7b23a15..00b841f 100644
--- a/README.md
+++ b/README.md
@@ -15,5 +15,14 @@ message size.
 ## Usage
 
 ```sh
-cargo run <message size in bytes>
+cargo run --release <message size in bytes>
 ```
+
+## Results
+
+A message size of 1024 bytes can be sufficient to trigger fragmentation when
+running an optimized build. Results from debug builds are hit-or-miss depending
+on the host system: they may have no issues with fragmentation regardless of
+message size, or they may encounter issues at closer to 4096 bytes.
+
+![Terminal screenshot showing results of running script with 512 and 1024 byte messages. The first run has no errors, while the second one displays two "out of order" warnings.](./screenshot.png)
diff --git a/screenshot.png b/screenshot.png
new file mode 100644
index 0000000..5dd6811
Binary files /dev/null and b/screenshot.png differ