Skip to content

Conversation

@mauroservienti
Copy link
Member

@mauroservienti mauroservienti commented Mar 10, 2025

This pull request adds a RavenDB dirty memory custom check. RavenDB dirty memory is the amount of data that needs to be flushed to disk. Flushing happens in a background thread. Under heavy load, that thread might be de-prioritized, causing the amount of dirty memory to increase. When that happens, shutting down the RavenDB (embedded) instance takes much time.

The custom check invokes a RavenDB HTTP admin endpoint (/admin/debug/memory/stats?includeThreads=false&includeMappings=false) to retrieve memory stats.

The custom check links to the documentation/guidance describing how to address/mitigate these scenarios.

@mauroservienti mauroservienti self-assigned this Mar 10, 2025
@mauroservienti mauroservienti changed the title Add a dirty memory custom check Add a RavenDB dirty memory custom check Mar 11, 2025
@mauroservienti mauroservienti force-pushed the dirty-memory-custom-check branch from 7544927 to 151e29d Compare March 12, 2025 15:02
@mauroservienti mauroservienti added this to the vNext milestone Mar 13, 2025
@mauroservienti mauroservienti marked this pull request as ready for review March 13, 2025 14:43
@mauroservienti
Copy link
Member Author

@andreasohlund @ramonsmits this is ready for a review

Co-authored-by: Andreas Öhlund <andreas.ohlund@particular.net>
@mauroservienti mauroservienti enabled auto-merge (squash) March 14, 2025 09:07
@mauroservienti mauroservienti merged commit aea8465 into master Mar 14, 2025
32 checks passed
@mauroservienti mauroservienti deleted the dirty-memory-custom-check branch March 14, 2025 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants