Here is the free tool for the stress testing in asp.net application.
https://learn.microsoft.com/en-us/archive/blogs/alikl/stress-test-asp-net-web-application-with-free-wcat-tool
Another is called asp.net performance engineering which will tell how we can stress application.
https://learn.microsoft.com/en-us/archive/blogs/alikl/asp-net-performance-engineering-stress-test-your-architecture-design-and-code
Also go through the following post:
Best way to stress test a website
From my experience before moving to the production environment please take of following things.
-
set debug=false into the web.config
-
set trace enabled=false into the web.config
-
Always use precompiled version of your code.
-
Compile your project into the release mode.
-
Publish your code if you are using asp.net 2.0 or higher version
-
User caching api as much as possible.
-
Decrease your html kb.
-
remove blank spaces from the asp.net html code.
-
Use stylesheet as external .css file
-
USE IIS Compression if poosible.
-
Put your javascript file in .js files
-
Use Server.Transfer instead of Response.redirect
-
Use Inproc Session State if possible.
-
Use Viewstate efficiently- Use controlstate instead of viewstate which is newer feature in asp.net 2.0
-
Avoid giving big name to controls it will increase your html kb.
-
Use Div instead of tables it will decrease your size.
-
Do IIS Performance tuning as per your requirement
Here is the good link that teaches us good way of deployment in production environment.
http://www.vbdotnetheaven.com/UploadFile/dsdaf/111222006014732AM/1.aspx