Other than session state what else in an asp.net application would use up server RAM?

Question

If I had 2 million users I've cached 1 mb's of data shared between all those users what else would use up RAM that each user would create?

EDIT: 2 million users login and have sessions at the same time, they are all making requests - maybe 10 requests per second. They are retrieving, for example, random numbers using a random number generator.

Not clear what you're asking: are you asking what things that would be created by users would use up RAM? — Ann L., Dec 11 '12 at 23:27
This is very vague question... even 100M users will not cause any server side usage if they don't make any requests... And if your server is purely stateless there still will be no per-user cost... — Alexei Levenkov, Dec 11 '12 at 23:36

score 0 · Answer 1 · edited May 23 '17 at 12:12

0

There is overhead for each request in a web application. It starts at the socket and works it's way up through IIS to ASP.NET to your application. You should look into performance monitoring. You can learn all sorts of neat things. Here is a good link for that:

How to Measure Memory Usage for a Live ASP.NET MVC Web Application

edited May 23 '17 at 12:12

Community

1
1

answered Dec 11 '12 at 23:37

Jake

82
3

Thanks Jake, I am asking specifically about RAM overhead. What would be stored in memory when a request is made? – user1809104 Dec 11 '12 at 23:40
Also, thanks for the link I however don't actually have a number of users to test how much memory is used. – user1809104 Dec 11 '12 at 23:45

score 0 · Answer 2 · answered Dec 11 '12 at 23:43

Best thing to do is look at your process yourself. Take a memory dump (using procdump or taskmgr) and then analyse it with windbg. This will show you exactly what is in memory on each heap and how much of it there is:

A good place to start is with the sos command !dumpheap -stat

Other than session state what else in an asp.net application would use up server RAM?

2 Answers2