The problem that the reader.read_thread parameter does not utilize as much as the actual number of nproc.

My CPU's thread count is 512 (I checked through the nproc command),
: 512 = 128core x 2 sockets x2(HyperThreading on)
It seems that this tool does not utilize as much as the actual number of nproc.
As you can see in the capture below, reader.read_threads parameter can only be allocated up to 128.

I checked again, and I think it only sweeps up to 128 threads in any environment. I don't know if it's a bottleleneck problem due to DLIO.
However, according to the run parameter guide you told me in #202, I think the total number of cores from the nproc command should be allocated to read_thread.

Could you check this problem?

Start by reviewing the run parameter guide referenced in #202 and reproduce the reported limit for reader.read_threads on a system where nproc reports more than 128. Trace where the parameter is bounded and compare that behavior with the available processor count. Done means the intended relationship between nproc and read_thread is documented or corrected and verified on a high-thread-count system.