Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We have a read-heavy zpool with some data that's used as part of our build process, on which we see a roughly 8x savings with dedup - and because of this ZFS dedup makes it economically viable for us to store the pool on NVMe rather than spinning rust.


And being read-heavy, suboptimal performance at write time is an infrequent pain, I guess?


Not even that - the data being written is coming straight from the network, and the pool has no issues keeping up.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: