memtx: introduce read view statistics #8510
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New entries have been added to
box.stat.memtx()
output:data
shows how much memory is allocated for memtx tuples:data.total
- total amount of memory allocated for data tuples. This includesdata.read_view
anddata.garbage
plus tuples that are actually stored in memtx spaces.data.read_view
- memory held for read views.data.garbage
- memory that is unused and scheduled to be freed (freed lazily on memory allocation).index
shows how much memory is allocated for memtx index extents:index.total
- total amount of memory allocated for indexing data. This includesindex.read_view
plus memory used for indexing tuples that are actually stored in memtx spaces.index.read_view
- memory held for read views.All numbers are given in bytes.
data.read_view
andindex.read_view
include memory allocated both for system read views (snapshot, replication) and user read views (EE-only). They should be non-zero only if there are open read views. To list all open read views, usebox.read_view.list()
.Closes #8501
Closes https://github.com/tarantool/tarantool-ee/issues/143