# "convert" process eating CPU **URL:** https://meta.discourse.org/t/convert-process-eating-cpu/101309 **Category:** Self-hosting **Created:** [November 5, 2018, 2:02pm UTC](https://meta.discourse.org/t/convert-process-eating-cpu/101309 "2018-11-05T14:02:19Z") **Posts on this page:** 1 **Showing post:** 14
### Author: ![skozz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/skozz/32/119704_2.png) [@skozz](https://meta.discourse.org/u/skozz) #### Post date: [February 27, 2019, 8:51am UTC](https://meta.discourse.org/t/convert-process-eating-cpu/101309/14 "2019-02-27T08:51:00Z")
Sorry for the delay, I was waiting to see if the last changes make an effect, and it does. Update: - I’ve upgraded the DO droplet to `16 GB Memory / 60 GB Disk / LON1 - Ubuntu Discourse on 14.04 ` - Change rebake to 1 - Increased workers from 5 to 8 following [your suggestion in another post](https://meta.discourse.org/t/spin-up-additional-sidekiq-workers/81707/2) 10 hours later 😊 ![26](https://global.discourse-cdn.com/meta/original/3X/7/3/739a309e7ce56e7439f62933a396dd9fc9c606bc.png) Now, I’ve updated the `rebake` to 10 and let’s see. I want to rebake all as before the _crisis_ and then back to my previous droplet. I think now is under control so thank you so much, everyone, for your time and suggestions, it has put me in the right way, and I learned a little bit more about how to manage this cases with Discourse. --- _[View the full topic](https://meta.discourse.org/t/convert-process-eating-cpu/101309)._