last time I looked at this, and it was a long time ago, it was around 10% and workload dependent. if you make direct and locking more robust, and allowed an ap

last time I looked at this, and it was a long time ago, it was around 10% and workload dependent. if you make direct and locking more robust, and allowed an application to turn off the kernel cache, you would only really need to interact with the filesystem after open in order to change your extents. +1. this is clearly a place where we can have nice things and performance