Lots of reasons. If crypto is part of the syscall path, then you definitely pay with latency. If you can push IO to a worker thread then you can release the us

Lots of reasons. If crypto is part of the syscall path, then you definitely pay with latency. If you can push IO to a worker thread then you can release the user call faster. This also requires tuning the read-ahead cache more aggressively. It could also be a change in crypto algorithm, unaligned page IO, or any other overlooked IO latency problems.