Hi,
There is some discussion around capacity here: UD Load Testing
But basically, if you’re expecting 50 concurrent users I think it’s do-able with the server spec you have.
Just consider the following:
-
Using session vars is fine for small bits of data, but for any large datasets I would consider using SQL. You can also leverage -serversideprocessing on udgrids which makes things super speedy (since it lets SQL do the pagination).
You just have to consider how you’re reading and writing, I wouldnt say you need to perform collect/submit at the end, but be wary of using the right indexing in your tables and ensuring you dont get any deadlocks - maybe make sure you’ve got the relevant error handling, try/catch blocks and retry functions to handle this if you do. -
It maybe also worth putting in a scheduled app pool recycle to have a ‘fresh start’ daily, I do this for mine to prevent the memory building up too high, I’ve got a scheduled endpoint which checks the app pool recycle time and broadcasts a message to all users to let them know this is happening (although not expecting people on at 3am)
I found that the bottle neck will usually be CPU before memory.