On Wednesday, January 11, 2017 at 2:46:14 PM UTC+5:30, [email protected] wrote: > I have an InfluxDB instance running in a linux vm (8 gb of ram and 4 cores). > > I am writing data to it over http from a message queue. > > My data structure written into influx looks like the following : > > > { > "measurement": "test", > "tags": { > "field1": integer, [range 0 - 50k] > "field2": integer, [range 1-10] > "field3": integer, [0/1] > "field4": integer,[0/1] > }, > > "fields": { > "field1": integer[0-99999999], > "field2":integer[0-99999999], > "field3":integer[0-20] > } > } > > When i query this series : > > a) select * from test order by time desc limit 1 - it takes around 5-6 > seconds to return > b) select * from test where time > [some recent timestamp] - it returns in > less than a second > > I have approximately 600k rows in my series. > > Is this some sort of a tuning problem? > Is it happening because of writing through the HTTP api into Influx very > frequently (at the rate of 5-6 writes/sec) ? > Is this related to the fact that each item in the series is storing a lot of > data? > > Thanks for any pointers you guys can provide.
There was maybe a slight change in perf after the upgrade but still query time > 4s. Anything else that you think might be going wrong here? -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/8972f46c-f27e-4f2c-91fd-b7dbe558ce33%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
