Thanks very much for your reply. One of the tags has about one hundred different values.
The result of the sql you mentioned is 11K. 在 2016年8月9日星期二 UTC+8上午4:58:19，Mike Schroll写道： > > Are any of your tags highly variable data? > > Search docs for cardinality to learn more. > > Run this command to return what your cardinality is: > SELECT sum(numSeries) AS "total_series" FROM "_internal".."database" WHERE > time > now() - 10s; > > On Tuesday, August 2, 2016 at 5:27:07 AM UTC-7, leidia...@gmail.com wrote: >> >> I am using influxdb 0.13. in Radhat 6.5 with 2 cpu and 4G memory. >> >> >> There are about 70 million points in one measurement. Each point has >> 4tags and 5 fields. It can excute count funtion without specify time >> window successfully. But when query "select * from measurement limit 10", >> influxdb eat up my memory and killed by systerm. And if i specify the time >> window, it runs fine. >> >> So, i wonder how the limit works. Why it eat up memory even though i >> limit the results to 10 >> > -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+unsubscr...@googlegroups.com. To post to this group, send email to influxdb@googlegroups.com. 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/3b16fc87-db2c-4833-acf7-00fef93c28f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
