Stux
MVP
- Joined
- Jun 2, 2016
- Messages
- 4,419
I would suggest running the tests with sync=always|standard|disabled
It might be that the default for a file extent is different to a zvol extent for instance.
Also, you might find ZFS is actually bottlenecked by either single-thread CPU performance, or Memory bandwidth. Haven't determined yet, but I see roughly twice the speed when benchmarking my 2.2Ghz dual channel Xeon, vs my 4ghz quad channel.
One peaks at circa 1GB/s
(same generation)
Did not look into file extents too much, but as the file extents are repeatedly mentioned as "just for dev testing", then it wouldn't surprise me if data reliability shortcuts are taken (for example, not actually sync writing data that needs to be sync written)
It might be that the default for a file extent is different to a zvol extent for instance.
Also, you might find ZFS is actually bottlenecked by either single-thread CPU performance, or Memory bandwidth. Haven't determined yet, but I see roughly twice the speed when benchmarking my 2.2Ghz dual channel Xeon, vs my 4ghz quad channel.
One peaks at circa 1GB/s
(same generation)
Did not look into file extents too much, but as the file extents are repeatedly mentioned as "just for dev testing", then it wouldn't surprise me if data reliability shortcuts are taken (for example, not actually sync writing data that needs to be sync written)
Last edited by a moderator: