# ¿El proceso del trabajador es más de lo definido?

**URL:** <https://meta.discourse.org/t/worker-process-is-more-than-defined/113230>\
**Category:** Self-hosting\
**Tags:** unsupported-install, hosting\
**Created:** [2 Abril, 2019 13:57 UTC](https://meta.discourse.org/t/worker-process-is-more-than-defined/113230 "2019-04-02T13:57:51Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Vencent](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vencent/32/120037_2.png) [@Vencent](https://meta.discourse.org/u/Vencent)\
**Post date:** [2 Abril, 2019 16:04 UTC](https://meta.discourse.org/t/worker-process-is-more-than-defined/113230/8 "2019-04-02T16:04:26Z")

</div>

> [@RGJ](#):
>
> You could probably get away with one unicorn (you have two now) and one sidekiq.

That is what I’m thinking. Does that mean my whole site will block if a single request is doing I/O (i.e. database read)? I’m not really familiar with the tech details in Discourse but it seems likely to happen.

---

_[View the full topic](https://meta.discourse.org/t/worker-process-is-more-than-defined/113230)._