Session CPU usage #707
Replies: 2 comments
-
The sesssions will be in "reconnection" cycle over and over again (because it doesn't have CPU time to send "ping" messages), you'll like loose messages or authentication (so you'll have to rescan QR for session to re-pair session) and the API will work slow
STOPPED one doesn't consume CPU, so that's fine!
Correct, only sessions in "running" block consume resources (CPU and Memory) 👇 |
Beta Was this translation helpful? Give feedback.
-
btw, we recommend doing "sharding" horizontal scaling like https://waha.devlike.pro/blog/waha-scaling-how-to-handle-500-sessions/#horizontal-scaling---sharding |
Beta Was this translation helpful? Give feedback.
-
The website states that a 4 GB server can handle around 50 NOWEB sessions. I am running my Waha instance on a 6 GB vps which I estimate can roughly handle around 75 sessions. Now, I wanted to ask if I exceed the number of sessions recommended, what are the potential problems this can cause? Also, most of my sessions are in the stopped state and logged out, so does that also take up any CPU usage or should I just take into calculation the sessions that are actively running? This is very important for me to manage the scalability of my application.
Beta Was this translation helpful? Give feedback.
All reactions