{
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-13",
  "slug": "submission-latency",
  "term": "Submission latency (fio)",
  "aliases": [
    "slat"
  ],
  "definition": "Submission latency in fio is the elapsed time from initialization of an I/O unit to an engine-dependent submission boundary.",
  "note": "For synchronous engines, slat ends just before the engine queue function is called; asynchronous timing differs [fio]. Preserve the engine and fio version. It is not an application-arrival clock, and its sample count need not be inferred from a different latency field.",
  "related": [
    "completion-latency",
    "latency-storage",
    "iops"
  ],
  "citations": [
    {
      "id": "fio",
      "title": "fio documentation: interpreting slat, clat and lat; engine-dependent timing boundaries.",
      "url": "https://fio.readthedocs.io/en/master/fio_doc.html",
      "accessed": "2026-10-13"
    },
    {
      "id": "hesela-populations",
      "title": "Hesela: fio summaries, latency sample populations and runtime denominators; synthetic examples.",
      "url": "https://hesela.com/analyses/storage-latency-coordinated-omission/#fio-populations",
      "accessed": "2026-10-13"
    }
  ]
}