Memory requirements for large app #572
-
|
I am building an app and as of now my waha instance is running on a vps with 4 vCPU cores, 6 GB RAM and 100 GB NVMe SSD storage. I store only session data and no media. As of now I am in developing the app but when it is deployed I will have well over 1000 instances running. What will be recommended memory requirements for it to function smoothly considering active use regularly. Also is x GB of NVMe storage better or 4x GB of SSD for the same price. Also should i stick to the $19 plan or will getting the $100 plan make a difference? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
|
Hi! It depends on what engine you're going to use - WEBJS (runs real browser) or NOWEB (works with websocket connections) I guess it'll be NOWEB, so anyway consider running TWO containers with ~500 sessions (or even split them into more smaller one), this way you'll avoid problems when one session goes crazy and affects all sessions at once (it doesn't happen frequently, but shit happens) Here's an article for that: We're also working on multiple workers on 1 database approach, will release it at the end of October 🤞
Here's the differences - https://waha.devlike.pro/pricing/ |
Beta Was this translation helpful? Give feedback.
-
|
Yes I am on Contabo and it's disappointing to know that after configuring everything it might not be good enough. What are other alternatives in similar price range? |
Beta Was this translation helpful? Give feedback.
-
|
I sometimes get a 500 internal server error and that's with just one instance running. I fixed it with exception handling and retry logic but I reckon it would pose a problem when the application is live. Do you think that's the Contabo going haywire? Also for multiple nodes do I need to purchase multiple waha images or one will work fine? |
Beta Was this translation helpful? Give feedback.
-
Hetner... it gives u a bit less specs than contabo but atleast more stable |
Beta Was this translation helpful? Give feedback.
-
|
what about netcup? any reviews? it's cheaper than Contabo as well surprisingly |
Beta Was this translation helpful? Give feedback.
-
Only issue with netcup is bad support... Let's keep the discussion relevant and if you have server related questions you can ask me on Discord: "cyborg" with underscore in start and end |
Beta Was this translation helpful? Give feedback.
Hi! It depends on what engine you're going to use - WEBJS (runs real browser) or NOWEB (works with websocket connections)
Here's answer about how many CPU/Memory you should have for that, based on # of sessions you'll have
https://waha.devlike.pro/docs/overview/faq/#how-much-cpu-and-memory-does-waha-consume
I guess it'll be NOWEB, so anyway consider running TWO containers with ~500 sessions (or even split them into more smaller one), this way you'll avoid problems when one session goes crazy and affects all sessions at once (it doesn't happen frequently, but shit happens)
Here's an article for that:
WAHA Scaling - How To Handle 500+ Sessions
We're also working on multiple workers on 1 dat…