elbencho VS ParallelReductionsBenchmark

You can also use elbencho (https://github.com/breuner/elbencho) which is functionally equivalent to IOR but a little more flexible.

I won't speak for him but Tallis is definitely aware (see his recent article on updated testing) and so are others. I regularly work with Sean Webster of Tom's Hardware (/u/TurboSSD) and we spend an insane amount of time working around SLC cache response and discussing it on my discord. These guys often use different tools (e.g. Iometer vs. FIO) although the one I've been playing with moving forward is elbencho. Either way, it's something that takes up a lot of time in SSD reviewer circles since it's a relatively tightknit group. It's a challenging topic especially as SLC caching algorithms are getting more complex, with behavioral and performance-based profiles and reviewers already doing preconditioning.

For the single threaded version, they have a data hazard on the sums that could be smoothed out with a little loop unrolling and separate variables.

But in the [threaded version](https://github.com/unum-cloud/ParallelReductions/blob/fd16d9...) they have separate slots for an accumulator but it's still in a shared vector, which most likely has the issue I described.