Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add page cache hit ratio to CMI #505

Merged
merged 2 commits into from
Oct 23, 2024
Merged

Add page cache hit ratio to CMI #505

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c61efb
Add page cache hit ratio to CMI
alexnb Oct 22, 2024
1b9a90c
fix metric name and title
alexnb Oct 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions modules/ROOT/pages/platform/metrics-integration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -387,6 +387,22 @@ This helps avoid unwanted pauses for garbage collection.
m| MAX
|===

.Page Cache Hit Ratio (per minute)
[frame="topbot", stripes=odd, grid="cols", cols="<1,<4"]
|===
| Metric name
m| neo4j_dbms_page_cache_hit_ratio_per_minute
| Description
| The percentage of times data required during query execution was found in memory vs needing to be read from disk.
Ideally the whole graph should fit into memory, and this should consistently be between 98% and 100%.
If this value is consistently or significantly under 100%, check the page cache usage ratio to see if the graph is too large to fit into memory.
A high amount of insert or update activity on a graph can also cause this value to change.
| Metric type
| _Gauge_
| Default aggregation
m| AVG
|===

.Page Cache Usage Ratio
[frame="topbot", stripes=odd, grid="cols", cols="<1,<4"]
|===
Expand Down