Spatial Database Performance Brief for Smart Property Platforms

Role: Principal GIS Database Architect with 12+ years optimizing geospatial indices for commercial real estate platforms.

Context

• Target Platform: {{platform_name}}
• Spatial Storage Engine: {{spatial_engine}}
• Portfolio Scale: {{property_dataset_size}} records
• Concurrency Demand: {{query_concurrency_target}} concurrent queries
• Response Benchmark: {{target_latency_ms}} milliseconds
• Core Workload: {{primary_geospatial_use_case}}

Task

Produce a concise spatial database optimization brief that assesses indexing strategies, hardware alignment, and polygon query tuning for {{platform_name}} to achieve the {{target_latency_ms}} target under heavy concurrency.

Method

1. Evaluate the spatial distribution and bounding-box density of {{property_dataset_size}} records inside {{spatial_engine}}.
2. Audit current geometric operator performance against {{primary_geospatial_use_case}} access patterns.
3. Benchmark R-Tree, PostGIS GiST, or spatial tile indexing alternatives suited for {{query_concurrency_target}}.
4. Calculate memory allocation requirements for caching spatial indexes in RAM.
5. Formulate query rewrite rules for spatial joins between parcel boundaries and active listings.
6. Establish a continuous VACUUM and spatial statistics update schedule.
7. Define monitoring thresholds for bounding-box search degradation.

Constraints

• MUST recommend concrete index types and parameters supported natively by {{spatial_engine}}.
• MUST NOT suggest full-table spatial re-projections at query runtime.
• All latency targets must strictly respect the {{target_latency_ms}} limit.
• Keep recommendations strictly scoped to database engine tuning and schema configuration.

Output format

• Section 1: Spatial Workload Profile (2 paragraphs)
• Section 2: Indexing Architecture & Schema Adjustments (bulleted specs with exact operators)
• Section 3: Engine Memory & Cache Tuning (table: Parameter, Target Value, Rationale)
• Section 4: Query Optimization Rules (3-5 concrete SQL/spatial optimization rules)

Self-review

• Verify that {{spatial_engine}} natively supports all proposed indexing methods.
• Ensure {{query_concurrency_target}} throughput requirements are addressed in cache calculations.
• Check that the total brief does not exceed 800 words.