Hi, To give more background this came about during an investigation into a slow offline compaction but it may affect any running FileStore as well (to be verified). I don't think it's related to oak-run itself, but more with the way we map files, and so far it looks like a bug (there is no reasonable explanation for mapping each tar file twice).
Took a quick look at the TarReader but there are not many changes in this area 1.0 vs. 1.4 branches. If no one has better ideas, I'll create an oak issue and investigate this a bit further. thanks, alex On Wed, Mar 22, 2017 at 4:28 PM, Ian Boston <[email protected]> wrote: > Hi, > I am looking at Oak-run and I see 2x the mapped memory between 1.0.29 and > 1.4.10. It looks like in 1.0.29 each segment file is mapped into memory > once, but in 1.4.10 its mapped into memory 2x. > > Is this expected ? > > Its not great for page faults. > Best Regards > Ian >
