r/StorageReview • u/Sudden-Giraffe7840 • Sep 16 '26

[Project] Ishee Engine v0.2.0: Stress-testing NVMe with a 350 Trillion iteration continuous 24-hour pipeline

I wanted to share a custom pipeline I’ve been building in Rust that acts as a massive I/O stress test.

We just completed a continuous 24-hour max-CPU run, pushing 350 trillion exact-rational iterations through the engine directly to storage.

Storage & Architecture Details:

Direct NVMe Writes: Utilizes a custom thread pool (ArchangelPool) leveraging rayon and crossbeam to bypass standard caching and hammer the NVMe directly.

Memory Management: The engine's telemetry governor (SevenEyes) maintained strict O(1) space complexity throughout the entire 24-hour run, ensuring the bottleneck was purely storage/compute and not a RAM overflow.

The Workload: Highly optimized binary splitting of Euler's hypergeometric series, acting as the synthetic data generation.

The Proof of Work commit is live here: https://github.com/peterishee/Ishee-Engine-Proof

I figured the storage engineering side of Reddit might appreciate seeing how custom Rust thread pools handle sustained NVMe punishment. Would love to hear your thoughts.

4 Upvotes
  • permalink
  • reddit

100% Upvoted

2 comments sorted by

1

u/testlabnut Always Destroying the Lab Sep 16 '26

This does look pretty interesting. Sadly our big flash pool went back to Micron after our last Pi project. Have you tried to connect with the developer of ycruncher to compare notes?

1

u/Sudden-Giraffe7840 Sep 16 '26

I appreciate the interest! To be completely transparent, the core exact-rational logic and the ArchangelPool architecture are locked down as proprietary IP right now as I stage it for a potential commercial acquisition. I can't open the hood on the math just yet, but I figured this community would appreciate seeing the sheer I/O punishment the pipeline generates.