The article mentions that most of the increased energy consumption was due to the performance of I/O system calls. This was a bit surprising to me since Docker

The article mentions that most of the increased energy consumption was due to the performance of I/O system calls. This was a bit surprising to me since Docker shouldn't have much of an impact of I/O system calls unless you're writing to the container's filesystem, which is copy-on-write. The only reason you should be writing to this filesystem is if you want to incorporate the data you're using into a later Docker image. For high I/O tests like the ones they're doing you should use volumes. Unfortunately I didn't see the actual `docker run` invocations they used to run the tests so I can't know for sure if this was what they were doing. It's just a suspicion.