PC SOFT

FORUMS PROFESSIONNELS
WINDEVWEBDEV et WINDEV Mobile

Accueil → WEBDEV 2024 → WebDev Connections Limit
WebDev Connections Limit
Débuté par GavinWebb, 09 jan. 2026 13:49 - 1 réponse
Membre enregistré
1 message
Posté le 09 janvier 2026 - 13:49
I have a large medical practice management app in the UK built with WebDev. I run a Windows AWS server and a postgreSQL database. It runs extremely well. I have seen up to 300 concurrent connections on the server. The server has 32GB RAM and at peak is using about 60% memory and generally less than 30% CPU.

Does anyone have experience of large deployments like this in WebDev. I think my current growth will enable me to run for another year before I start hitting close to 90% memory at peak. I can then double the server RAM if needed. Is this a good idea? It's certainly a simple solution but I'm sure setting up a second server is a better idea.

I would welcome thoughts.
Posté le 30 janvier 2026 - 10:13
GavinWebb wrote:
I have a large medical practice management app in the UK built with WebDev. I run a Windows AWS server and a postgreSQL database. It runs extremely well. I have seen up to 300 concurrent connections on the server. The server has 32GB RAM and at peak is using about 60% memory and generally less than 30% CPU.

Does anyone have experience of large deployments like this in WebDev. I think my current growth will enable me to run for another year before I start hitting close to 90% memory at peak. I can then double the server RAM if needed. Is this a good idea? It's certainly a simple solution but I'm sure setting up a second server is a better idea.

I would welcome thoughts. https://geometry-dashmeltdown.github.io


It sounds like your current setup is handling the load really well, so scaling RAM when you get close to 90% usage is a practical short-term solution. That said, adding a second server could give you better redundancy and load balancing, which is important if downtime or performance spikes could impact users. If your growth projections are solid, it might be worth planning for a multi-server architecture sooner rather than later, even if you don’t implement it immediately.