Files
geointel/docs/specs/PERFORMANCE_BUDGETS_CANONICAL.md
Jens faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
Initial public release
2026-08-31 21:56:53 +02:00

921 B

Canonical Performance Budgets

These are V1 local-development budgets. They are guidance, not hard production SLAs.

API responsiveness

  • simple GET list/detail: < 500 ms on demo data;
  • project/area creation: < 1 s;
  • metadata retrieval: < 500 ms once extracted;
  • job status polling: < 300 ms.

Processing budgets on demo fixtures

  • vector metadata extraction: < 2 s;
  • vector clip on demo area: < 5 s;
  • raster metadata extraction on small GeoTIFF: < 3 s;
  • tile manifest generation on demo raster: < 10 s;
  • QA/QC on demo building fixtures: < 5 s;
  • GeoJSON export on demo fixtures: < 5 s.

UI budgets

  • initial shell render: < 2 s in local dev;
  • map layer toggle on demo data: < 500 ms;
  • metrics panel update after API response: < 300 ms.

Scaling note

Large real rasters or full municipality layers may exceed these budgets. In that case, the app must show async job state rather than blocking.