Open ericboucher opened 6 years ago
Once we're using an API to compute driving distances / times, less time will be spent on calculations made within the database (compared to the total calculation time). Accordingly, the performance gains from resolving this issue may not be as dramatic as tweaks made to API usage.
Using geometry data with the appropriate map projection will lead to faster geospatial queries in Postgres. One such query is currently ~50% of the time for the haversine-based adequacy calculation.
We should
Note that the second step above might cause temporary downtime for the app, since the database is a shared resource.