journalRemoveFromPageCache default value probably we should set to false?

**BUG REPORT**

***Describe the bug***
The configuration is as follows:
journalDirectories=/data1/bk-journal
ledgerDirectories=/data2/bk-data,/data3/bk-data,/data4/bk-data
data1\data2\data3\data4 are all physical disks.
Online, we found that when read miss cache(At this time, data2~4 disks will have more reads.). At this time, the flush time of data1 increases：

The indicator bookie_journal_JOURNAL_SYNC is mainly for the time-consuming statistics of the method org.apache.bookkeeper.bookie.JournalChannel#forceWrite:

Since the journal disk is independent, the bc.forceWrite time-consuming should not be affected. So I suspect that NativeIO.bestEffortRemoveFromPageCache takes time to increase. I'm not particularly sure, but I have a guess: Due to a large amount of disk data being read, the pagecache is affected, which leads to an increase in the time required to call the bestEffortRemoveFromPageCache method here?

So in order to prevent reads from affecting writes, should the default value of journalRemoveFromPageCache be set to false?