-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Low query performance of 0.9.6 dealing with high res time series #5351
Comments
I know they recommend not having the WAL on the same disk as the data.
You could try moving that. |
@xrl what are the machine specs of the InfluxDB server, and how many points per second are the telegraf sources writing? What are some actual queries and their response times from the logs? |
if viewing a large timespan of data that is granular 10s interval, you might want to create a continuous query. another fix, Perhaps try tweaking auto in the "GROUP BY time(auto)" I wish grafana's group by time(auto) was 1/2 as granular by default, |
This should be fixed after #5196 is merged. |
wow that's A pull request. |
Closing since the new query engine has been merged and there are no steps to reproduce this issue. |
I am using telegraf to instrument 15 or so servers with a 10s sampling interval. The influxdb host started off very responsive and able to return results for large timespans. Now it is very slow and I am forced to change my time range down to 30 minutes to get a reasonable response time. I am using Grafana 2.5 to query influxdb.
You can see the influx and telegraf configs here: https://gist.github.com/xrl/4dddb71eabd606304065
The text was updated successfully, but these errors were encountered: