You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The queries made using the streaming API endpoints (data by date range) comes in too slow. Queries may need to be executed concurrently (with a limit) and glued together in the right order if performance can't be found otherwise.
Additionally, the front-end dashboard may need to do a better job caching results so that it can simply make requests for any missing data. For example, it might only need one or two days of results in a month because it already cached the other 28 days. Multiple requests could even be made to fill in the "gaps" of missing data.
-- This was with regard to Postgres. It needs to be re-built and re-tested using InfluxDB. The thinking was the concurrently make multiple queries to Postgres and/or to utilize partitioning.
The text was updated successfully, but these errors were encountered:
The queries made using the streaming API endpoints (data by date range) comes in too slow. Queries may need to be executed concurrently (with a limit) and glued together in the right order if performance can't be found otherwise.
Additionally, the front-end dashboard may need to do a better job caching results so that it can simply make requests for any missing data. For example, it might only need one or two days of results in a month because it already cached the other 28 days. Multiple requests could even be made to fill in the "gaps" of missing data.
-- This was with regard to Postgres. It needs to be re-built and re-tested using InfluxDB. The thinking was the concurrently make multiple queries to Postgres and/or to utilize partitioning.
The text was updated successfully, but these errors were encountered: