Last post Feb 03, 2011 09:34 AM by atconway
Jan 31, 2011 07:45 AM|johnfoot|LINK
What are the typical hardware (including memory) for a standard ASP.NET application. I know it depends on the complexity of the application, but I am referring to a simple travel engine / booking application where most of the users are expected to just
browse and a few will make reservations only. Initially we are not expecting a high number of hits on this also.
Jan 31, 2011 08:06 AM|Yasser Shaikh|LINK
Usually you try it out on different hardware and keep note on how well it runs.
From that you'll be able to deduce what is needed or recommended.
I am not aware of other methods.
Certainly you can't go around and say "Hey, this IL instruction here will totally need a Pentium 4"
Hope this would help :)
Jan 31, 2011 08:07 AM|Yasser Shaikh|LINK
http://bytes.com/topic/net/answers/113367-hardware-requirement-net-framework-server-client check this link too.
Jan 31, 2011 08:12 AM|shabirhakim1|LINK
Exactly what you know .It depends type of application and its content/Hits expectation....
I suggest you to start from standard webserver next you can scale up ....
what ever you can see all these discussion here
Feb 03, 2011 09:34 AM|atconway|LINK
What are the typical hardware (including memory) for a standard ASP.NET application.
These forums are for software and this one specifically for "Software Architecture" rather than "Hardware Architecture" which is what you are looking for, so I would be careful on advice given from us software folks ;) With that said, if you do not have
a hardware person to consult with, there are a few "beginner" steps you could take to get up a solid standing server.
Again, this advice comes from a "Sunday Mechanic" of sorts when it comes to hardware requirments and my specialty is in software
not hardware. Taking metrics on the server is highly reccomended as well to see how it is preforming under load once configured. There are also configurations in the machine.config file (threads allocated, timeouts, etc) or app.config
at a lower level that can affect the performance of the individual app.
I recommend you re-post this question on the TechNet forums where those guys eat, sleep, and breathe server configuration, or the IIS forums for that configuration as well.
Hope this helps!