Hi Kevin,
Thanks for posting in the community!
From your description, you're doing stress testing on a certain ASP.NET web
application. The application used sqlserver connections to a certain
database(aspstate). However, you found that when running the test, the
connections remains abou 100 and then the web app's performance(pages
request per unit time) slow down to barely nothing.
If there is anything I misunderstood, please feel free to let me know.
As for this issue, I'd like to asked some further questions on it:
1. Are you using the SQLServer as the ASP.NET web application's Session
State management server? If so , would you provide me the detailed setting
for the <sessionState> in your web.config file, especially the connection
string?
2. Have you used the SQLProfiler to see what's the account the ASP.NET used
to connect sqlserver? Also, what's the web app's authentication setting?
Have you used impersonate?
In addition, here are some tech articles on server process monitor and
sqlserver session management:
#Watching Your Server Processes
http://msdn.microsoft.com/library/en...chserverproces
ses.asp?frame=true
#ASP.NET Performance Monitoring, and When to Alert Administrators
http://msdn.microsoft.com/library/en...rf.asp?frame=t
rue
#HOW TO: Configure ASP.NET for Persistent SQL Server Session State
Management
http://support.microsoft.com/default...b;en-us;311209
Please check out the preceding suggestions. If you have any new findings or
further infos , please feel free to post here.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx