# Ruby multi-CPU threading

**URL:** <https://meta.discourse.org/t/ruby-multi-cpu-threading/248433>\
**Category:** Migration\
**Tags:** rails-console, drupal\
**Created:** [December 9, 2022, 10:41pm UTC](https://meta.discourse.org/t/ruby-multi-cpu-threading/248433 "2022-12-09T22:41:51Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [December 10, 2022, 12:04pm UTC](https://meta.discourse.org/t/ruby-multi-cpu-threading/248433/7 "2022-12-10T12:04:24Z")

</div>

I want to mention two things.

- Yes, CPUs matter, so just get a bigger VPS and run multiple sidekiq instances for rebaking and image processing, it will go faster
- When your import is totally completed it’s always a good idea to do a backup / restore, it will give you better database performance.

These two together: get a big VPS for the import and when you’re done move it to a smaller production VPS (using backup and restore).

Generally an import will not require you to rebake posts afterwards.

---

_[View the full topic](https://meta.discourse.org/t/ruby-multi-cpu-threading/248433)._