This issue has to be looked from a micro and macro level. On the microlevel
the best way is workload specific. On the macro level this mostly boils
down to data and memory size.
Companions are going to churn cache, this is unavoidable. Imho solid state
makes the micro optimization meanless in the
On Thu, Dec 6, 2012 at 7:36 PM, aaron morton aa...@thelastpickle.com wrote:
So for memory mapped files, compaction can do a madvise SEQUENTIAL instead
of current DONTNEED flag after detecting appropriate OS versions. Will this
help?
AFAIK Compaction does use memory mapped file access.
The
Will MMapping data files be detrimental for reads, in this case?
No.
In general, when should we opt for MMap data files and what are the factors
that need special attention when enabling the same?
mmapping is the default, so I would say use it until you have a reason not to.
mmapping will
