# Running netdata with cpu affinity

**URL:** <https://community.netdata.cloud/t/running-netdata-with-cpu-affinity/864>\
**Category:** Help\
**Tags:** agent, agent-configuration\
**Created:** [February 3, 2021, 12:12pm UTC](https://community.netdata.cloud/t/running-netdata-with-cpu-affinity/864 "2021-02-03T12:12:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shohamd](https://avatars.discourse-cdn.com/v4/letter/s/67e7ee/32.png) [@shohamd](https://community.netdata.cloud/u/shohamd)\
**Post date:** [February 3, 2021, 12:12pm UTC](https://community.netdata.cloud/t/running-netdata-with-cpu-affinity/864/1 "2021-02-03T12:12:10Z")

</div>

Hi,  
I want to start using netdata to monitor my servers.  
I’m planning to run netdata with docker.  
Most of my servers are running other docker containers that are running latency-critical processes that are running on specific CPUs (configured with isolcpus).  
Is there any way to control the affinity of netdata threads? I don’t want netdata to run on all the isolcpus cores, or even make it run only on a specific core (core 0 for example).

Thanks,  
Doron

---

<div class="post-metadata">

**Author:** ![Austin\_Hemmelgarn](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/austin_hemmelgarn/32/4495_2.png) [@Austin\_Hemmelgarn](https://community.netdata.cloud/u/Austin_Hemmelgarn)\
**Post date:** [February 5, 2021, 12:29pm UTC](https://community.netdata.cloud/t/running-netdata-with-cpu-affinity/864/2 "2021-02-05T12:29:43Z")

</div>

We don’t currently support any special configuration to do this, meaning you will have to use whatever your normal tooling for setting up Docker containers is to configure it. For k8s that would mean CPU Manager functionality. For regular Docker, there’s a `--cpuset` option for the `docker run` command (and I believe an equivalent for Docker Compose). For Docker Swarm there appears to be no option for this right now.