Expose max auto resizes metric

Currently, only the number of auto resizes is exposed as a metric.
When this value reaches 0 it is no longer possible to
expand the cache.

However, it is not possible to know the maximum number of auto-resizes
that the cache could go through.

Expose the maximum number of auto-resizes as a metric, so that can be
used together with the remaining auto-resizes to evaluate the overall
utilization of the cache.

Bug: Issue 15458
Change-Id: Ie81684950a28f3e2420bddfcaa10b7db218d00fb
3 files changed
tree: 8d9f3a5169959584086f3e1257f71ee549946456
  1. src/
  2. .gitignore
  3. BUILD
  4. external_plugin_deps.bzl
  5. Jenkinsfile
  7. README.md

Persistent cache for Gerrit, based on ChronicleMap

Non-blocking and super-fast on-disk cache libModule for Gerrit Code Review based on ChronicleMap on-disk implementation.

How to build

This libModule is built like a Gerrit in-tree plugin, using Bazelisk. See the build instructions for more details.


  • Install cache-chronicalmap module

Install the chronicle-map module into the $GERRIT_SITE/lib directory.

Add the cache-chroniclemap module to $GERRIT_SITE/etc/gerrit.config as follows:

  installModule = com.googlesource.gerrit.modules.cache.chroniclemap.ChronicleMapCacheModule

For further information and supported options, refer to config documentation.

Migration from H2 caches

You can check how to migrate from H2 to chronicle-map here.