# Does Discourse require 2GB to work "Lag Free"?

**URL:** <https://meta.discourse.org/t/does-discourse-require-2gb-to-work-lag-free/25278>\
**Category:** Feature\
**Created:** [Février 16, 2015, 5:41 UTC](https://meta.discourse.org/t/does-discourse-require-2gb-to-work-lag-free/25278 "2015-02-16T05:41:21Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [Février 16, 2015, 10:37 UTC](https://meta.discourse.org/t/does-discourse-require-2gb-to-work-lag-free/25278/8 "2015-02-16T22:37:43Z")

</div>

Puma is usable, in fact it is in our Gemfile. But as it stands now you would need 2 processes, one for puma and one for sidekiq, both of which would share no memory.

So that adds up to say 400MB RSS and that is even before postgres and redis.

That said, puma would be more “laggy” due to the GIL and lack of out-of-band GC. You may get similar throughput, but time per request would vary a lot more.

---

_[View the full topic](https://meta.discourse.org/t/does-discourse-require-2gb-to-work-lag-free/25278)._