Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make streaming API faster #1

Open
tmaiaroto opened this issue Oct 16, 2014 · 0 comments
Open

Make streaming API faster #1

tmaiaroto opened this issue Oct 16, 2014 · 0 comments

Comments

@tmaiaroto
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant