Is there a way to control memory and disk quota?

[ppazos]

With quota I mean to have a config option that allows to set the max amount of memory and disk a repo could use, and provide some kind of check and alert/exception when close to the quota or when the quota has been reached.

Thanks!

[fh-ms]

To control memory consumption, you can configure the LazyReferenceManager when working with Lazy references.

For disk space monitoring, we don't have built-in capabilities. Nonetheless, the housekeeping logic cleans up the used disc space as efficiently as possible.

[ppazos]

Hi @fh-ms what does it mean to have "... a memory quota of 0.75"?

Is that a percentage of a total? Where is the total defined? What happens when the quota is reached? Does it automatically store to disk?

[fh-ms]

If that quota is reached, the LazyReferenceManager will clear the subgraphs under Lazy references and free up memory.
Whereby the least used Lazy references will be cleaned up first, meaning the 'hot' data will stay in memory.

The quota is in relation to the committed memory.
The committed size is the amount of memory guaranteed to be available for use by the Java virtual machine.

[ppazos]

Thanks @fh-ms is that documented?