u/Henrik716

Getting a self-hosted geospatial API to cold start in 1.3s on a single core

Getting a self-hosted geospatial API to cold start in 1.3s on a single core

Wrote up the engineering work behind running pygeoapi on ephemeral Fly.io microVMs for Waystones Cloud. Single CPU core, scale-to-zero.

Five issues we hit: a POSIX file truncation race on the OpenAPI endpoint, a self-deadlocking warmup script, why we generate the OpenAPI document in TypeScript rather than Python, CPU scheduling conflicts with nice -n 19, and a frontend timing gap.

https://waystones.cloud/blog/cold-start-optimization

u/Henrik716 — 13 days ago