{
  "slug": "byte-hit-ratio",
  "term": "Byte hit ratio",
  "aliases": [
    "byte-hit ratio",
    "byte hit rate"
  ],
  "definition": "Byte hit ratio is the fraction of requested payload bytes served from a cache under a stated request-accounting rule.",
  "note": "For full-object requests, divide hit payload bytes by total requested payload bytes, counting repeated requests each time. Request hit ratio counts hits rather than bytes, so differently sized objects can reverse a ranking. [size-aware]\n\nTen requests totaling 24 KiB can yield eight hits serving 8 KiB or two hits serving 16 KiB. These fixed-residency examples produce byte hit ratios of one-third and two-thirds respectively. [hesela]",
  "related": [
    "cache-admission",
    "tinylfu",
    "mapping-cache"
  ],
  "citations": [
    {
      "id": "size-aware",
      "title": "Einziger, Eytan, Friedman and Manes. Lightweight Robust Size Aware Cache Management. arXiv:2105.08770v2 (2021), sections 4-5.",
      "url": "https://arxiv.org/pdf/2105.08770v2",
      "accessed": "2026-10-16"
    },
    {
      "id": "hesela",
      "title": "Hesela. Fixed-residency request and byte accounting: constructed inputs and reproducible results.",
      "url": "https://hesela.dev/research/cache-metrics.json",
      "accessed": "2026-10-16"
    }
  ],
  "provenance": [
    "Payload accounting alone does not measure latency, compressed transfer, partial-read traffic or NAND operations. The example is synthetic, not a cache-policy benchmark. [hesela]"
  ],
  "status": "research",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-16"
}