umgeher/leveled
0
Fork 0
Code Issues Pull requests Releases Activity Actions

Make page cache level configurable

Browse source
This commit is contained in:
Martin Sumner 2019-07-25 12:23:10 +01:00
parent 6cd898b731
commit 57d73fc548
3 changed files with 30 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

12
priv/leveled_multi.schema
View file

@ -66,7 +66,7 @@
{datatype, integer}
]}.
%% @doc The approximate size (in bytes) when a Journal file should be rolled.
%% @doc The approximate count of objects when a Journal file should be rolled.
%% This time measured in object count, a file will be rolled if either the
%% object count or the journal size limit is reached. Default 200K.
%% Note that on startup an actual maximum size will be chosen which varies by
@ -77,6 +77,16 @@
{datatype, integer}
]}.
%% @doc The level of the ledger to be pre-loaded into the page cache
%% Depending on how much memory is available for the page cache, and how much
%% disk I/O activity can be tolerated at startup - then the level at which the
%% ledger is forced into the page cache can be controlled by configuration.
{mapping, "multi_backend.$name.leveled.ledger_pagecachelevel", "riak_kv.multi_backend", [
{default, 4},
{datatype, integer}
]}.
%% @doc The number of journal compactions per vnode per day
%% The higher the value, the more compaction runs, and the sooner space is
%% recovered. But each run has a cost