Teardown №1
A measurement study of a hosted image generation API, built to turn “it feels fast” into numbers.
- subject
- fal-ai/flux/dev
- work
- Measurement harness & report
- scope
- 47 calls · 5 experiments
- status
- Shipped · 2026
The inference segment reported in the existing latency study.
Standard deviation: 9.9 msQuestion
01A benchmark answers which model is better. What happens inside the one you already chose?
Teardown is a measurement study of a hosted inference API (fal.ai's flux endpoint) instrumented from a browser the way an integrator would hit it.
Anyone who has waited for a generation and wondered what the wait was made of. Anyone building on one of these APIs, who has to pick a default and cannot pick it from the documentation.
Instrumentation
0247 structured calls across five experiments, with measurements logged to disk. Select an experiment to see the question it asks.
what does another step cost, and what does it buy?
sweep → diff → time → log → publish
step sweep / image change + inference time
guidance sweep / adjacent image differences
seed repeats / hashes + pixel differences
latency series / segment timing + variability
friction log / documentation versus behaviorMethod summary from the existing case study, not a source-code excerpt.
Measurements
03Segment timings and image differences are separate measurements. The figures below preserve the recorded values and sample sizes from the existing report.
Segment medians cannot be added to obtain end-to-end p50. End-to-end p95/p99 and the sampling window are not documented in the local case-study data.
Latency anatomy
Inference against steps
Adjacent step differences
Seed determinism
Key decisions
04Measure the integration path
WhyThe harness reaches a hosted API from the browser, as an integrator would.
Trade-offThese results describe this integration and model, not every deployment.
Separate timing from image change
WhyLatency, step sweeps, guidance sweeps and seed comparisons answer different questions.
Trade-offA faster response is not itself a measure of image quality.
Publish the measurement scope
WhyThe latency series, step comparisons and repeated seed runs have different sample sizes.
Trade-offA small study supports specific observations, not universal guarantees.
Findings
05F1 / The hidden segment
Queue sd 277 ms against inference sd 9.9. The segment carrying nearly all the variance is the one the response body never returns.
F2 / Identical bytes
Three runs, three different inference times, one sha256, zero of 262,144 pixels different. Determinism holds and the documentation never says so.
F3 / Past 28
S20 to S28 moves 7.655 percent of pixels. The next eight steps move 1.488.
F4 / No resting point
No adjacent guidance pair falls below 17.167 percent, and the last rung still moves 57.591. It never converges.
Designed / Built
06Designed
The interactive report and its reading order: questions, measurement methods, figures and findings.
Built
A browser-based measurement harness using TypeScript, React and the fal API, with five experiments and measurements logged to disk.
Next teardown
07TEARDOWN № 1 is the first in a series. The method, sweep and diff and time and log and publish with sources, ports to any inference API. The findings do not: they are one model, measured.
The next subject has not been announced in this case study.