All news

How omic run got to eight seconds

412 cases in 8.2 seconds. The engineering behind response caching, concurrency caps, and skipping unchanged work.

412 cases in 8.2 seconds. The engineering behind response caching, concurrency caps, and skipping unchanged work.

How omic run got to eight seconds

The homepage number is real: 412 cases in 8.2 seconds. It started at ninety. This is where the time went.

Cache what didn’t change

An unchanged case against an unchanged model is not worth re-running. Responses are cached by a hash of the full request, so a typical run only pays for what moved.

Concurrency without rate-limit roulette

Cases run concurrently under a cap you tune to your provider limits. Retries are automatic and budgeted, so one flaky request doesn’t fail the suite.

Skip the scoring too

Deterministic scorers re-run for free, but judged scorers are cached with the response. The expensive path only fires on new output.

More from Omic

Create a free website with Framer, the website builder loved by startups, designers and agencies.