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

Record time to calculate compation run

Browse source 
As this is a factor in assessing suitability of Journal size
This commit is contained in:
Martin Sumner 2018-09-26 10:19:24 +01:00
parent 8d8a0a3f5b
commit 3df481941f
3 changed files with 9 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/STARTUP_OPTIONS.md
View file

@ -21,7 +21,7 @@ If there are smaller objects then lookups within a Journal may get faster if eac
- excessive CPU use and related performance impacts during rolling of CDB files, see log `CDB07`;
- excessive load caused during journal compaction despite tuning down `max_run_length`.
If the store is used to hold bigger objects, the `max_journalsize` may be scaled up accordingly. Having fewer Journal files (by using larger objects), will reduce the lookup time to find the right Journal during GET requests, but in most circumstances the impact of this improvement is marginal.
If the store is used to hold bigger objects, the `max_journalsize` may be scaled up accordingly. Having fewer Journal files (by using larger objects), will reduce the lookup time to find the right Journal during GET requests, but in most circumstances the impact of this improvement is marginal. The primary impact of fewer Journal files is the decision-making time of Journal compaction (the time to calculate if a compaction should be undertaken, then what should be compacted) will increase. The timing for making compaction calculations can be monitored through log `IC003`.
## Ledger Cache Size