I need to run InfluxDB alongside other processes and need to ensure that it 
doesn't consume all of the available CPU on the server impacting other critical 
processes...    

At the moment in my testing I see InfluxDB occupy up to 100% of both available 
cores if I run a query that retrieves a lot of historical data.   I can spec a 
server with additional cores, but I'm concerned that it will still be possible 
for InfluxDB to use all of them if e.g. multiple users run long historical 
queries at the same time.   Is there a way to limit e.g. the number of cores 
that InfluxDB will use?

-- 
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 [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/aec62a88-b7aa-4092-9dfc-f29c9b856b1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to