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
35 lines
1.1 KiB
Markdown
35 lines
1.1 KiB
Markdown
# Performance Budgets
|
|
|
|
GeoIntel will eventually process large geospatial files. V1 must make limits explicit.
|
|
|
|
## V1 file limits
|
|
|
|
- Default max upload: 500 MB.
|
|
- Raster preview should not load full large raster into frontend memory.
|
|
- Backend metadata extraction should stream or sample where possible.
|
|
|
|
## Processing rules
|
|
|
|
- Long operations must become jobs after foundation is complete.
|
|
- V1 can run small fixture operations synchronously if documented.
|
|
- Tile generation should avoid keeping all tiles in memory.
|
|
|
|
## Frontend budgets
|
|
|
|
- Avoid rendering thousands of features directly without simplification/clustering.
|
|
- Use map layers for GeoJSON, not huge DOM lists.
|
|
- Paginate dataset and analysis lists if needed.
|
|
|
|
## Database indexes
|
|
|
|
Required indexes:
|
|
|
|
- spatial index on `areas.geometry`
|
|
- spatial index on `vector_features.geometry`
|
|
- spatial index on `detections.geometry`
|
|
- foreign key indexes for project/dataset/analysis lookups
|
|
|
|
## Known V1 limitation
|
|
|
|
Full production-scale remote sensing processing is not required in V1. The product must demonstrate correct architecture and working small/medium workflows.
|