Is Wisej tool is suitable for a system with large number of users

The key point here is memory usage. I’ll make a test about memory growth.

Thanks Luca,

The 4000 user app has about over 1000 controls (in about 10 “forms” composing a large screen) and about 2-4 large datagrids open at any given time. It’s an heavy system. I don’t know exactly the usage pattern but I don’t think the 4000 are concurrent.

In general the apps we see have extremely complex screens with hundreds if not thousands of controls. See http://madewithwisej.com and the case studies pages. There are some new ones being prepared as well.

In any case, to estimate the memory usage I recommend to create about 10 sessions and get them to the average usage. Call GC.Collect(), log the total memory, add 10 more sessions doing the same (you can do it all in one browser just by creating new tabs, or put the session timeout to a high value and keep creating sessions on from a single client). Then call GC.Collect() again and log the memory differential and divide by 10.

It gives you roughly an idea of the memory growth rate. The reason to do it like that is that Wisej shares a lot of memory across all sessions so the early memory growth is irrelevant being the footprint.

Don’t worry about CPU power. All you need to do for the CPU is to set the minThreadCount to a higher number, probably 200 or 300 to avoid the thread starvation problem.

I’d guess that in your case 2 servers are plenty.

Do you mean 4000 concurrent users (using the app at the same time)? In practice, the number of screens open at the same time is more important than the number of screens in the app. I understand that the memory consumed by data sets is more important than the amount of memory consumed by screens (forms, controls, events, etc.). In this case, we can say that an application that does not open large number of screens at the same time and does not use very large data sets, 2 or 3 64GB 8 cpu processors can easily run 10000 users (or more?). If my conclusion is correct, I found the answer I was looking for.

Thank you Luca,

Depends on the application.

We have systems in production with 800+ screens and 4,000 users on 2 64Gb servers. Or 1500+ screens and 700 users on 1 server.

I don’t see any issue with 10-20 screens and unless the app creates huge data sets and keeps them in memory. In which case there are many simple ways to change it.

In terms of traffic and CPU usage Wisej uses far less than other systems since the packets are very small and the processing is limited to the specific event instead of rebuilding the whole page like Blazor. In terms of memory in small tests we see much less usage than Blazor.