Hello! I don't have a problem per-se but I'm running into something that maybe is some noob-ness on my side. At my organization we are using InfluxDB (right now the 1.0) for our monitoring metrics for over an year now without complaints. Really well done! Since we are in the IoT sensor business we came up with possibly using InfluxDB to store our sensor raw data and use it as our main DB (not the current scenario at the moment). I've setup a simple testing scenario with a single node (8 core, 16GB RAM box, InfluxDB 1,1) and inserted 15M rows into a single measurement with 2 tags and 3 fields which models perfectly our data. Although this is a small data-set it would serve its purpose as a "milestone 0" kind of thing.
Using chunked queries I've reached a read speed of about 1M rows every 15 seconds. Changing the size of the chunks alters the behavior but doesn't really do anything speed wise. It's this an expected read speed for this kind of scenario? I'm using the autogen retention policy no configuration tuning whatsoever. I will gladly supply any more information anyone needed, as we are, again, really happy with InfluxDB and would really like to unify our operational DB needs. -- 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/7ab4b1fc-3280-497c-9730-b973abb52122%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
