# Ruby multi-CPU threading **URL:** \ **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:** 4
**Author:** ![marianord](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marianord/32/90502_2.png) [@marianord](https://meta.discourse.org/u/marianord)\ **Post date:** [December 10, 2022, 3:17am UTC](https://meta.discourse.org/t/ruby-multi-cpu-threading/248433/4 "2022-12-10T03:17:14Z")
The tasks that take a long time to restore are indeed multi-threaded. One caveat is that 2x the CPUs almost never is 2x the performance. Other point is that usually the tasks for `rake posts:rebake` and the heavy lifting of the forum itself to _recover_ and optimize the content can happen with the forum live. Which might reduce the time you need to have the forum either off-line or read-only and be able to offer a somewhat degraded experience. My recommendation would be: first, test. Do the migration, see how much times it takes and how the forum looks without all the rebakes in place. If it’s good enough time the migration to end around the lower traffic time of your forum that way you _earn_ some 4-10h of migration without a lot of people complaining. --- _[View the full topic](https://meta.discourse.org/t/ruby-multi-cpu-threading/248433)._