On Fri, Apr 10, 2020 at 02:44:55PM +0800, Qu Wenruo wrote:
On 2020/4/10 下午2:34, Xing Zhengjun wrote:
> Hi Wenruo,
> We test it in v5.6, the issue still exist, do you have time to take a
> look at this? Thanks.
This is expected.
The extra check brings new overhead mostly equal to another CRC32 run.
We believe it's worthy, as our read time tree checker has exposed quite
some bit flip corruption.
The test probably runs on a PMEM device so there's no slowdown from the
actual IO and the in-memory checks are measurable, though 28% is a lot,
I'd expect something like 5-10% at most.