Initial public release
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
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
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
# Performance Budgets
|
||||
|
||||
## API
|
||||
- health endpoint: < 200ms local
|
||||
- project list: < 500ms for 100 projects
|
||||
- dataset metadata: < 500ms after extraction
|
||||
- synchronous upload response: should register file quickly and hand off heavy work to job queue
|
||||
|
||||
## Raster
|
||||
- never load large rasters fully into memory for preview;
|
||||
- prefer windowed reads and overviews;
|
||||
- large tiling must run as background job.
|
||||
|
||||
## Vector
|
||||
- use spatial indexes for intersection/QA operations;
|
||||
- simplify only for display, not source-of-truth unless explicitly stored as derived layer.
|
||||
|
||||
## Frontend
|
||||
- initial app load should not require heavy GIS data;
|
||||
- map layers should be lazy-loaded;
|
||||
- large GeoJSON should be paged, tiled, or simplified.
|
||||
|
||||
## Jobs
|
||||
Long-running operations must have status transitions:
|
||||
`queued -> running -> succeeded|failed|cancelled`.
|
||||
Reference in New Issue
Block a user