I wrote a Rust script in 10 minutes or so that processes several GiB's big ISO files and it calculates its values so fast, that most time is spent waiting for the HDD! Look at the CPU usage and the disk read/write stats :D

(No, the picture is not fake, it's a real screenshot from my desktop edited with Gimp)

So i/o constrained then

36 MiB/s? On rather big iso files? If your shit isn't completely fragmented that should be almost sequencial reading
Get a new hdd, that's 2008 speeds

@Kimmax it's also writing, as far as I know HDDs slow down massively with concurrent read/write ops?

@RememberMe is correct. The process would be much faster if he holded as much as possible in RAM and only writed after it had been finished (or there was no RAM left).
Or, you know, with and SSD...
The main problem with concurrent read/write processes on a HDD is that the spinning reader has to constantly jump between different disk positions.

@RememberMe good point
In that case, as @Benedikt said, buffering is the solution. I'd add a user configurable memory threshold and use as much memory as possible
Any chance we could get hold of the script? Would love to tinker with it

> 'script'
> proceeds to name a compiled, native systems programming language

@Kimmax https://gist.github.com/kangalioo/...