update documentation based on test results

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)

src/main.rs

@@ -7,7 +7,7 @@ use std::{
     time::{Duration, Instant},
 };
 
-const DURATION_MS: u64 = 5000;
+const DURATION_MS: u64 = 1000;
 const BIND_ADDR: &str = "127.0.0.1:7000";
 
 fn main() {