# Worker process is more than defined?

**URL:** <https://meta.discourse.org/t/worker-process-is-more-than-defined/113230>\
**Category:** Self-hosting\
**Tags:** unsupported-install, hosting\
**Created:** [April 2, 2019, 1:57pm 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:** 11

<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:** [April 2, 2019, 4:16pm UTC](https://meta.discourse.org/t/worker-process-is-more-than-defined/113230/11 "2019-04-02T16:16:17Z")

</div>

> [@Vencent](#):
>
> I also heard it’s better to disable swap on a Kubernetes node.

Yes, but that’s in the same league as “it’s better to have more RAM” .  
And if you don’t have more RAM then you should have swap as a fallback.

> [@Vencent](#):
>
> my whole site will block if a single request is doing I/O (i.e. database read)?

No, it won’t be THAT bad.  
But you said you had really low traffic…

---

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