# Moet ik Discourse opnieuw opbouwen na het opschalen van mijn DigitalOcean Droplet?

**URL:** https://meta.discourse.org/t/do-i-need-to-rebuild-discourse-after-upscaling-my-digitalocean-droplet/274183
**Category:** Self-hosting
**Created:** [7 augustus 2023 om 12:11 UTC](https://meta.discourse.org/t/do-i-need-to-rebuild-discourse-after-upscaling-my-digitalocean-droplet/274183 "2023-08-07T12:11:28Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![earlysound](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/earlysound/32/319316_2.png) [@earlysound](https://meta.discourse.org/u/earlysound)
#### Post date: [7 augustus 2023 om 12:11 UTC](https://meta.discourse.org/t/do-i-need-to-rebuild-discourse-after-upscaling-my-digitalocean-droplet/274183/1 "2023-08-07T12:11:28Z")

</div>

I recently upscaled my DigitalOcean droplet, which hosts my Discourse instance. Initially, the droplet had 2GB of RAM and 1 vCPU. I’ve now upgraded it to 8GB with 4 vCPUs.

Is it necessary to rebuild Discourse to take full advantage of the increased resources? Or will Discourse automatically utilize the additional RAM and CPU without any further action on my part?

Any insights or best practices related to this would be greatly appreciated!

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [7 augustus 2023 om 12:27 UTC](https://meta.discourse.org/t/do-i-need-to-rebuild-discourse-after-upscaling-my-digitalocean-droplet/274183/2 "2023-08-07T12:27:42Z")

</div>

You might want to consider at least quadrupling your:

`UNICORN_WORKERS:`

in app.yml and restarting the container …

as per:

> [@Rescaling the server, which configs need to be changed? - unicorn workers, memory, etc](https://meta.discourse.org/t/rescaling-the-server-which-configs-need-to-be-changed-unicorn-workers-memory-etc/252788/2):
>
> I usually specify two `unicorn_workers` per core, and 25% of the system memory as `db_shared_buffers`

or you can run `./discourse-setup` as per @pfaffman on that very same topic.
