Skip to content

Model heat-aware admission and SSD write pressure offline - #36

Merged
FujitsuPolycom merged 4 commits into
mainfrom
codex/heat-ssd-research
Sep 6, 2026
Merged

Model heat-aware admission and SSD write pressure offline#36
FujitsuPolycom merged 4 commits into
mainfrom
codex/heat-ssd-research

Conversation

@FujitsuPolycom

@FujitsuPolycom FujitsuPolycom commented Aug 30, 2026

Copy link
Copy Markdown
Owner

Resulting behavior

Adds an offline, GPU-free research model for bounded hit heat, verified-restore recomputation savings, shared-trunk reference value, marginal retained-byte cost, simplified TinyLFU trace replay, hourly and daily staged-write budget reports, logical-to-host write-amplification estimates, and NVMe SMART Data Units Written deltas.

The research package is excluded from SparkCache wheels and runtime source identities. CI runs its tests separately and a static regression rejects imports from serving modules.

Technical reason

SparkCache retention uses TTL and manifest-recency LRU. Operators can observe device endurance, but the serving connector exposes publication-byte telemetry but does not implement frequency-aware admission, write-budget enforcement, or cache-attributed physical writes. The offline model makes those policy inputs testable without allowing advisory metadata to affect restore eligibility or inference.

Compatibility

Cache identity, digest salts, chunk geometry, manifest schemas, and on-disk namespaces are unchanged. No serving configuration, connector behavior, package artifact, image, or deployment profile changes. Heat metadata cannot make cached state eligible for restoration.

Status and limitations

Research-only. Budget reports do not enforce limits. TinyLFU evaluation is a simplified shadow model. Publication byte values are caller-supplied. Serving reports expose committed unique and staged bytes; automated ingestion into this research ledger is not implemented. SMART parsing consumes an operator-supplied 512-byte log page; it does not acquire device telemetry. Data Units Written measures quantized host writes for the whole device, not NAND-media amplification or directory-specific writes.

Validation

  • python -m pytest research -q: 22 passed
  • python -m pytest sparkcache deploy research -q: 1,123 passed, 8 skipped after integration with main
  • python -m ruff check .: passed

Provide bounded hit counters, verified-span savings, shared-object cost accounting, TinyLFU shadow replay, staged-write budget reports, write-amplification estimates, and NVMe SMART counter parsing outside the shipped SparkCache package. Document the serving integration prerequisites and unsupported enforcement boundaries. Cache identity and on-disk namespaces are unchanged. Validate the prototype independently and preserve the pinned deployable-source hash.
Identify committed unique bytes and staged write bytes already exposed by serving reports. Keep research-ledger ingestion and budget enforcement explicitly unsupported, and replace the obsolete fixed performance threshold with matched workload evidence requirements. No cache identity or runtime changes. Validation: 1123 tests passed, 8 skipped across sparkcache, deploy, and research.
@FujitsuPolycom
FujitsuPolycom marked this pull request as ready for review September 6, 2026 19:05
@FujitsuPolycom
FujitsuPolycom merged commit 48bbd2b into main Sep 6, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant