MESHTEN LAB•Graphics & Engine
September 28, 2026•Soak Benchmark
Automated 30-Minute Engine Soak Testing: Measuring Frame Latency and Memory Drift
Continuous headless playtesting on Crown and Claim (native Vulkan): sub-8ms worst-frame latency and zero private memory leaks.
Core Finding:Short 30-second rendering benchmarks often mask slow-burn memory leaks, shader cache thrashing, and asset streaming degradation. In Atlas Engine, we deployed autonomous playtest agents to execute continuous 30-minute traversals (9.5+ km across 53 streaming regions), measuring steady sub-8ms worst-frame p50 latencies and zero private byte accumulation.
Worst-Frame p50 Latency
7.88 ms
Median worst-case frame time held comfortably under the 8.33 ms (120 fps) budget ceiling.
Private Memory Growth
-0.08 MB / min
Private byte allocation was flat over 30 minutes, confirming zero memory leaks.
Input Delivery Ratio
0.9997
Continuous agent input delivery was maintained with zero command buffer dropped packets.
Clean Swapchain Frames
900 / 900 Frames
Full sampled presentation window presented without fallback skips or tearing.
Empirical Findings Table
Soak test telemetry across 1,800 seconds and 9,595 meters traversal| Telemetry Metric | Measured Value | Context & Observability |
|---|---|---|
| Worst-Frame p50 Latency | 7.88 ms | Median worst-case frame time held comfortably under the 8.33 ms (120 fps) budget ceiling. |
| Private Memory Growth | -0.08 MB / min | Private byte allocation was flat over 30 minutes, confirming zero memory leaks. |
| Input Delivery Ratio | 0.9997 | Continuous agent input delivery was maintained with zero command buffer dropped packets. |
| Clean Swapchain Frames | 900 / 900 Frames | Full sampled presentation window presented without fallback skips or tearing. |
Engineering Action Directives
- Autonomous agent playtesting running continuous multi-kilometer traversals can effectively surface memory leaks and frame budget outliers that short benchmarks miss.
- Maintaining flat memory allocation over extended continuous traversal provides strong operational evidence against uncollected resource leaks.
Methodology Boundaries & Limits
- 30-minute soak duration: While sufficient to detect linear memory leaks, long-term 24-hour endurance soaks are needed to identify rare accumulation defects.
- Headless execution: Tested via headless and automated agent navigation; interactive player input variance and erratic camera motions may trigger different rendering paths.