# mongodb qan-agent 1.5.2 high cpu

**URL:** <https://forums.percona.com/t/mongodb-qan-agent-1-5-2-high-cpu/6064>\
**Category:** PMM 1.x\
**Created:** [December 8, 2017, 9:59am UTC](https://forums.percona.com/t/mongodb-qan-agent-1-5-2-high-cpu/6064 "2017-12-08T09:59:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bedonath](https://avatars.discourse-cdn.com/v4/letter/b/bbe5ce/32.png) [@bedonath](https://forums.percona.com/u/bedonath)\
**Post date:** [December 8, 2017, 9:59am UTC](https://forums.percona.com/t/mongodb-qan-agent-1-5-2-high-cpu/6064/1 "2017-12-08T09:59:20Z")

</div>

Hi,

I have installed PMM on our internal MongoDB 3.4.10 ubuntu cluster and noticed that the client consumes a lot of resources. This is affecting MongoDB operation execution times in a way that we basically can not use it with our current virtual hardware specs. Having a closer look at one of the the nodes (in this case one of the MongoDB config servers) I realized that this is caused by the percona-qan-agent which seems to use a lot of the cpu time. Stopping the mongodb:queries service with ‘sudo pmm-admin stop mongodb:queries’ brings down the cpu usage to a ‘normal’ level. The remaining two services ‘mongodb:metrics’ and ‘linux:metrics’ behave as expected. I have checked the logs in /var/log but could not find anything suspicious. Whether profiling in MongoDB is enabled or disabled does not really seem to change this. Can anybody give some advice?

Thanks, Bernd