# Unexpected CPU usage by RabbitMQ (beam.smp) under no load

**URL:** <https://community.taiga.io/t/unexpected-cpu-usage-by-rabbitmq-beam-smp-under-no-load/1053>\
**Category:** Self hosted Taiga\
**Tags:** docker\
**Created:** [April 17, 2023, 6:53am UTC](https://community.taiga.io/t/unexpected-cpu-usage-by-rabbitmq-beam-smp-under-no-load/1053 "2023-04-17T06:53:06Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![viamonster](https://avatars.discourse-cdn.com/v4/letter/v/7993a0/32.png) [@viamonster](https://community.taiga.io/u/viamonster)\
**Post date:** [July 25, 2023, 5:47am UTC](https://community.taiga.io/t/unexpected-cpu-usage-by-rabbitmq-beam-smp-under-no-load/1053/16 "2023-07-25T05:47:40Z")

</div>

Was this issue ever resolved, @vcarceler @daniel.herrero?

Because we are seeing a similar behavior of beam.smp using an disproportional amount of system resources.

---

_[View the full topic](https://community.taiga.io/t/unexpected-cpu-usage-by-rabbitmq-beam-smp-under-no-load/1053)._