You can probably use the taskset command to limit the influxdb process to specific cores.
On Friday, August 5, 2016 at 10:45:19 AM UTC+2, [email protected] wrote: > > 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/387a5529-a81d-4358-af3d-f136858d37d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
