# High CPU usage (Ruby)

**URL:** https://meta.discourse.org/t/high-cpu-usage-ruby/348913
**Category:** Support
**Tags:** server-resources
**Created:** [January 25, 2025, 1:50am UTC](https://meta.discourse.org/t/high-cpu-usage-ruby/348913 "2025-01-25T01:50:40Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [January 25, 2025, 9:22am UTC](https://meta.discourse.org/t/high-cpu-usage-ruby/348913/3 "2025-01-25T09:22:44Z")

</div>

Yep. I also suggest decreasing the number of unicorn workers:

> [@How to avoid upstream timeouts?](https://meta.discourse.org/t/how-to-avoid-upstream-timeouts/35483/4):
>
> General advice is **one worker per CPU core (real or logical)**. I would allow at least 512mb ram per worker as well, so here is hoping you have at least 512mb times the number of logical cores on your server

---

_[View the full topic](https://meta.discourse.org/t/high-cpu-usage-ruby/348913)._