Menu

Individual skill

fast-experiments

0upvotes

Use when designing or auditing a USENIX FAST storage evaluation, covering real devices and firmware, device-state control (aging, preconditioning, fill, TRIM), standard workloads and traces (SNIA IOTTA, YCSB, filebench, fio), write amplification, tail latency, endurance and wear, crash-consistency testing, fair baselines, and matching the metric to the shape of each storage claim.

FAST-Skills/skills/fast-experiments/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# FAST Experiments

Use this before submission when the storage evaluation is not yet locked. FAST reviewers are storage
people; the evaluation is where a good idea is won or lost, and the questions are storage-specific.
The organizing principle is **measure the storage cost you claim to change, on real hardware in a
realistic state** — not a throughput bar on a fresh drive.

## Evaluation audit

- **Match the metric to the storage claim.** A claim about *endurance* needs bytes-written / P/E
  cycles, not throughput; a claim about *responsiveness* needs **tail latency** (p99/p99.9), not the
  mean; a claim about *space* needs measured on-media footprint; a claim about *durability* needs a
  crash-consistency test. The wrong metric is the most common FAST reject.
- **Use real devices, and name them.** Model, capacity, interface (SATA/SAS/NVMe), and — critically
Back to top