update documentation based on test results

This commit is contained in:
Brent Schroeter 2026-03-13 22:45:49 +00:00
parent 52f1dbe7a2
commit 591e2d37b4
2 changed files with 10 additions and 1 deletions

View file

@ -15,5 +15,14 @@ message size.
## Usage ## Usage
```sh ```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)

BIN
screenshot.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 116 KiB