CacheMetrics: expose request count for cache sizing decisions

Cache hit ratio alone is insufficient for deciding which caches should
be grown. A rarely accessed cache may have a poor hit ratio because most
lookups are first-time accesses, so increasing its size provides little
benefit.

Expose the total request count alongside existing cache metrics so cache
growth decisions can be prioritized based on both hit ratio and access
volume. This is especially useful when storage constraints prevent
growing every cache, allowing heavily used caches with lower hit ratios
to be prioritized over infrequently accessed caches.

Release-Notes: Emit caches/memory_request_count and caches/disk_request_count metrics
Change-Id: I4714615892e4b8c89a040851760539d3fab6bb28
2 files changed
tree: 0dfe1052a645f3b57738e5bb41de4008c3bb3dd6
  1. .agents/
  2. .gemini/
  3. .github/
  4. .settings/
  5. .ts-out/
  6. antlr3/
  7. configs/
  8. contrib/
  9. Documentation/
  10. e2e-tests/
  11. java/
  12. javatests/
  13. lib/
  14. modules/
  15. plugins/
  16. polygerrit-ui/
  17. prolog/
  18. prologtests/
  19. proto/
  20. resources/
  21. tools/
  22. webapp/
  23. .bazelignore
  24. .bazelproject
  25. .bazelrc
  26. .bazelversion
  27. .editorconfig
  28. .git-blame-ignore-revs
  29. .gitignore
  30. .gitmodules
  31. .gitreview
  32. .mailmap
  33. .pydevproject
  34. .zuul.yaml
  35. AGENTS.md
  36. BUILD
  37. COPYING
  38. external_deps.lock.json
  39. INSTALL
  40. Jenkinsfile
  41. MODULE.bazel
  42. MODULE.bazel.lock
  43. package.json
  44. pnpm-lock.yaml
  45. pnpm-workspace.yaml
  46. README.md
  47. SUBMITTING_PATCHES
  48. web-dev-server.config.mjs
  49. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

Objective

Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.

Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

Gerrit is the work of hundreds of contributors. We appreciate your help!

Please read the contribution guidelines.

Note that we do not accept Pull Requests via the Github mirror.

Getting in contact

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

The instruction how to configure GerritForge/BinTray repositories is here

On Debian/Ubuntu run:

    apt-get update && apt-get install gerrit=<version>-<release>

NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.

On CentOS/RedHat run:

    yum clean all && yum install gerrit-<version>[-<release>]

On Fedora run:

    dnf clean all && dnf install gerrit-<version>[-<release>]

Use pre-built Gerrit images on Docker

Docker images of Gerrit are available on DockerHub

To run a CentOS 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.