Open SolomidHero opened 1 year ago
@SolomidHero If you are running on an ext4
filesystem, your benchmark is probably flawed: ext4
inserts invisible fsyncs for existing files.
If you close()
existing files after writing them from scratch, or atomic-rename something replacing them, ext4 will insert an fsync()
!
Sources:
auto_da_alloc
I hit this confusing issue when first benchmarking piz
. @mrkline The README should mention this issue.
Try run both unzip benchmarks in an empty directory to be sure.
I tried to decompress .zip with many small files on aws ec2 instance.