# UploadCreator omzeilen voor import

**URL:** <https://meta.discourse.org/t/bypass-uploadcreator-for-import/174833>\
**Category:** Product Support\
**Created:** [2 januari 2021 om 23:50 UTC](https://meta.discourse.org/t/bypass-uploadcreator-for-import/174833 "2021-01-02T23:50:33Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Ghan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ghan/32/177964_2.png) [@Ghan](https://meta.discourse.org/u/Ghan)\
**Post date:** [9 januari 2021 om 17:09 UTC](https://meta.discourse.org/t/bypass-uploadcreator-for-import/174833/8 "2021-01-09T17:09:54Z")

</div>

> [@pfaffman](#):
>
> you could contrive to run multiple processes

It seems that as posts are processed for attachments, there are a number of sidekiq jobs that get spun up to deal with some other processing on these posts. As a result, even a single process working on attachment imports manages to slowly drive the server to over 40 load average even with 8 cores. (I increased the number of sidekiq workers to handle the load.)

I might be able to stop the unicorn service until the import is complete, but that is just shifting the load to a later time. It seems like the processing has to be done one way or the other.

---

_[View the full topic](https://meta.discourse.org/t/bypass-uploadcreator-for-import/174833)._
