32 ms·

"You can install a Zulip server on a system with 2G of RAM, but for production use we recommend a system with 4GB of RAM or more." Something has gone horribly

by krig 11y ago

"You can install a Zulip server on a system with 2G of RAM, but for production use we recommend a system with 4GB of RAM or more." Something has gone horribly wrong when a chat server can barely run on 2G. edit: As a frame of reference, here's what Inspire IRCd needs: > A network with 3000-4000 locally connected clients and 10000 open channels experiences a constant 1-4% CPU use with 70MB of RAM use. This won't go up drastically, but it will go up. Around 40000 local clients means you'll be expecting some 500MB of RAM. [1] [1]: http://www.inspircd.org/wiki/FAQ.html http://www.inspircd.org/wiki/FAQ.html

tabbott 11y ago
See https://news.ycombinator.com/item?id=10280246 https://news.ycombinator.com/item?id=10280246. Historically most users were using the single cloud installation at zulip.com, and so having this significant fixed memory overhead wasn't a problem. I expect someone will do the work the fix this before long; it shouldn't be hard.
- krig 11y ago
  Thanks for the explanation! I take it that the open sourced zulip is very close to what zulip.com runs, then?
  - tabbott 11y ago
    Yes, it's in fact exactly what's running on zulip.com. puppet/zulip_internal in the server repo even has the zulip.com puppet configuration (sans secrets).
CydeWeys 11y ago
Who cares though? A 4 GiB stick of ECC server RAM is $35-50, which is only about $10 more expensive than a 2 GiB stick. If you spent even twenty minutes of developer time trying to reduce memory usage, you've already lost money. It may still be worth the total savings if someone solves it globally, but from the perspective of an individual company who wants to run this, it doesn't matter at all.
tabbott 11y ago
Posting this in a few places since it came up N times on this thread: I opened https://github.com/zulip/zulip/issues/34 https://github.com/zulip/zulip/issues/34 to track optimizing the server-side memory consumption. :)

by krig 11y ago

tabbott 11y ago

See https://news.ycombinator.com/item?id=10280246 https://news.ycombinator.com/item?id=10280246. Historically most users were using the single cloud installation at zulip.com, and so having this significant fixed memory overhead wasn't a problem. I expect someone will do the work the fix this before long; it shouldn't be hard.

krig 11y ago
Thanks for the explanation! I take it that the open sourced zulip is very close to what zulip.com runs, then?
- tabbott 11y ago
  Yes, it's in fact exactly what's running on zulip.com. puppet/zulip_internal in the server repo even has the zulip.com puppet configuration (sans secrets).

CydeWeys 11y ago

Who cares though? A 4 GiB stick of ECC server RAM is $35-50, which is only about $10 more expensive than a 2 GiB stick. If you spent even twenty minutes of developer time trying to reduce memory usage, you've already lost money. It may still be worth the total savings if someone solves it globally, but from the perspective of an individual company who wants to run this, it doesn't matter at all.

tabbott 11y ago

Posting this in a few places since it came up N times on this thread: I opened https://github.com/zulip/zulip/issues/34 https://github.com/zulip/zulip/issues/34 to track optimizing the server-side memory consumption. :)