we have loaded tickdata for 2 years with separate measurement per symbol. ( no tags defined)
select 3 fields causing enormous swapping of about 6 GBS and ultimately our PCO host with 24 GB ram is swapping heavily we are using influxdb 1.4.2
select “bid-price”,“ask-size”,“last-price” from “” where time >=‘2016-01-01T00:00:00Z’ and time <= now() limit 0
we have no tags and assuiming time is a tag so this query should not do table scan !
I was wondering if its possible to limit the memory overtake by a single query and enforce data results pushed out on a per chunk basis.