views:

144

answers:

2

Hai guys,

I want to know,is memory management a concern with asp.net mvc..

  • comparision of memeory management in both asp.net mvc and web forms by experts
A: 

It depends on the application, if you have a standard application you rarely have to worry about memory.

==EDIT==
Surely the memory management is how you set up and configure IIS, if your application follows best practice and has no performance issues, this will be up to the IIS configuration settings and how much memory is allocated. Therefore is it up to the MVC application or the way IIS is configured I should have stated that above.

Burt
Hai burt, What happens if get 200 - 500 users in a minute
Pandiya Chendur
You always have to worry about memory, but ASP.NET MVC is not any different than Webforms in this aspect.
Vilx-
ok vilx i saw in asp.net forums about some comparision of memory management between asp.net mvc and webforms
Pandiya Chendur
Could you give a link?
Vilx-
http://forums.asp.net/p/1488120/3489866.aspx
Pandiya Chendur
I think the conclusion was that the Castle framework (whatever that is) was to blame, not .NET itself.
Vilx-
+3  A: 

AFAIK there is no difference in worrying about memory in ASP.NET MVC and webforms. You have to do it in both cases. :)

To elaborate, they both are built on top of the same ASP.NET infrastructure, which is built on top of the .NET runtime. Thus, they use the same memory management as any other .NET application, web or otherwise.

The overhead of the frameworks themselves is negligible, the real memory usage will come from the objects YOU load in your application. If you get a lot of users (from comments - 200 to 500 per minute), you will need to think about scaling out horizontally. That is, having multiple web and DB servers (also known as a "cluster"). This requires a bit of thought from the very beginning of the development, but is not very difficult to do. There should be other resources on this subject which is outside of the scope of this question.

Vilx-