)]}'
{
  "commit": "f80f56cde56d690cc7f1030c034238074efbc10a",
  "tree": "0dfe1052a645f3b57738e5bb41de4008c3bb3dd6",
  "parents": [
    "4e65a3cc306184820b9a6ba0e4bf116484471fad"
  ],
  "author": {
    "name": "Adithya Chakilam",
    "email": "achakilam@nvidia.com",
    "time": "Mon Jul 13 19:49:43 2026 -0500"
  },
  "committer": {
    "name": "Adithya Chakilam",
    "email": "achakilam@nvidia.com",
    "time": "Tue Jul 14 12:19:05 2026 -0500"
  },
  "message": "CacheMetrics: expose request count for cache sizing decisions\n\nCache hit ratio alone is insufficient for deciding which caches should\nbe grown. A rarely accessed cache may have a poor hit ratio because most\nlookups are first-time accesses, so increasing its size provides little\nbenefit.\n\nExpose the total request count alongside existing cache metrics so cache\ngrowth decisions can be prioritized based on both hit ratio and access\nvolume. This is especially useful when storage constraints prevent\ngrowing every cache, allowing heavily used caches with lower hit ratios\nto be prioritized over infrequently accessed caches.\n\nRelease-Notes: Emit caches/memory_request_count and caches/disk_request_count metrics\nChange-Id: I4714615892e4b8c89a040851760539d3fab6bb28\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7da1c18de4cfd51becafc191607f0af77e93cdbf",
      "old_mode": 33188,
      "old_path": "Documentation/metrics.txt",
      "new_id": "5c13aef7bac95a81da93f5568d367ba661a4832a",
      "new_mode": 33188,
      "new_path": "Documentation/metrics.txt"
    },
    {
      "type": "modify",
      "old_id": "7053df0eb0dbfb2539a83353ff2eea6935e94c76",
      "old_mode": 33188,
      "old_path": "java/com/google/gerrit/server/cache/CacheMetrics.java",
      "new_id": "e6dd0a73545c7a01d8cf1ab0faefe67542a90bcf",
      "new_mode": 33188,
      "new_path": "java/com/google/gerrit/server/cache/CacheMetrics.java"
    }
  ]
}