{
  "slug": "tape-speed-matching",
  "term": "Tape speed matching",
  "aliases": [
    "dynamic speed matching"
  ],
  "definition": "Tape speed matching adjusts a drive's transport speed and native data rate toward the effective host data rate to reduce rate-mismatch backhitches.",
  "note": "Matching compares native rate with host delivery after accounting for data compressibility. Application bytes before in-drive compression and native-rate bytes are different accounting bases; compare equivalent byte rates before diagnosing a mismatch. For a fixed compression ratio C defined as host-input bytes divided by compressed bytes, a host write rate H supplies H / C on the native byte basis. Sustaining a minimum native rate R therefore needs H >= C * R in this constant-rate accounting model; this is not a throughput benchmark or a complete streaming guarantee. [ibm-matching] [ibm-compression]\n\nExample: assuming R = 120 MB/s and C = 2, the required H is 240 MB/s; H = 200 MB/s supplies only 100 MB/s native, a 20 MB/s shortfall. MB/s is decimal; these are assumed inputs, not drive specifications.\n\nAvailable operating rates depend on the drive and cartridge format. A finite buffer can absorb temporary interruptions, but matching does not promise continuous streaming at arbitrarily low input rates. A larger nominal buffer is not proof of a particular stall tolerance. [ibm-matching] [ibm-control]\n\nSynchronization can cause repositioning independently of slow delivery. Speed matching does not by itself change what a write acknowledgement guarantees or prove that buffered data reached the medium; separate accelerator features address synchronization-related backhitches. [oracle-sync]",
  "status": "shipping",
  "advantages": [
    {
      "text": "Can reduce repositioning caused by host/drive rate mismatch within the drive's supported operating range.",
      "citationIds": [
        "ibm-matching"
      ]
    }
  ],
  "limitations": [
    {
      "text": "Supported rates and control behavior are implementation-specific; a vendor speed table is not a measurement of an application's backup throughput.",
      "citationIds": [
        "ibm-matching"
      ]
    }
  ],
  "related": [
    "tape",
    "lto",
    "tape-backhitch"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-28",
  "citations": [
    {
      "id": "ibm-matching",
      "title": "IBM TS2900: Speed matching, native rates and data compressibility",
      "url": "https://www.ibm.com/docs/en/ts2900tapeautoloader?topic=features-speed-matching",
      "accessed": "2026-10-27"
    },
    {
      "id": "ibm-control",
      "title": "Katagiri and Oe, US8035912B2: System and method for controlling traveling of tape, Background",
      "url": "https://patents.google.com/patent/US8035912B2/en",
      "accessed": "2026-10-27"
    },
    {
      "id": "oracle-sync",
      "title": "Oracle T10000 Systems Assurance Guide: File Sync Accelerator and Tape Application Accelerator",
      "url": "https://docs.oracle.com/cd/E48725_03/TTKSA/chapter1.htm",
      "accessed": "2026-10-27"
    },
    {
      "id": "ibm-compression",
      "title": "IBM Support: A Faster Tape Drive or Media Does Not Necessarily Mean Better Overall Performance",
      "url": "https://www.ibm.com/support/pages/node/645567",
      "accessed": "2026-10-28"
    }
  ],
  "provenance": [
    "IBM LTO and Oracle T10000 examples are different product families, not one interchangeable device specification."
  ]
}