Request Current
in [ASP .NET]
|
From: Johan Karlsson on 6 Apr 2010 01:44 Hi! I'm sorry for the delay of the answer, I've been on a four day vacation in a cabin without electricity. I tried the following settings and it seems to mitigate the issue. What settings are recommended? <serviceThrottling maxConcurrentCalls="100" maxConcurrentSessions="100"/> The call to the service is through a session-enabled webservice to keep the calling user authenticated. I also lowered the rate of calls to the webservice. Thanks /Johan "Allen Chen [MSFT]" <allenc(a)online.microsoft.com> skrev i meddelandet news:9FraoRk0KHA.2348(a)TK2MSFTNGHUB02.phx.gbl... > Hi Johan, > >>I've have an asp.net application that calls a backend service hosted in > IIS >>using WCF. I'm having some performance issues that seems to be related to >>hitting the maximum number of connections. > >>My initial question is: > >>The Request Current counter in ASP.NET never drops to zero. It gets stuck > at >>a minimum of 1-4. When the counter goes up to about 19-20 the application >>locks. It looks like its the backend service that locks up since other >>applications get a timeout calling other methods. > >>Should the Request Current counter drop to zero or is it normal that it >>stays at 1-4? > > Do you have any progress on this issue? > > Regards, > Allen Chen > Microsoft Online Support >
From: Allen Chen [MSFT] on 7 Apr 2010 21:37 Hi Johan, >I tried the following settings and it seems to mitigate the issue. What >settings are recommended? ><serviceThrottling maxConcurrentCalls="100" maxConcurrentSessions="100"/> The answer is it depends. If your server is very powerful you can set it a bit larger. These settings are used to prevent server from resource exhaustion. My suggestion is to do some load tests to decide what value to set in your scenario. Please feel free to ask if you have additional questions. Regards, Allen Chen Microsoft Online Support Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com.
From: Johan Karlsson on 8 Apr 2010 02:15 Hi! I'll do that. What seems weird is that the calls take longer than expected and there is no locking in the database? // Johan "Allen Chen [MSFT]" <allenc(a)online.microsoft.com> skrev i meddelandet news:T01LKwr1KHA.3664(a)TK2MSFTNGHUB02.phx.gbl... > Hi Johan, > >>I tried the following settings and it seems to mitigate the issue. What >>settings are recommended? > >><serviceThrottling maxConcurrentCalls="100" maxConcurrentSessions="100"/> > > The answer is it depends. If your server is very powerful you can set it a > bit larger. These settings are used to prevent server from resource > exhaustion. My suggestion is to do some load tests to decide what value to > set in your scenario. > > Please feel free to ask if you have additional questions. > > Regards, > Allen Chen > Microsoft Online Support > > Delighting our customers is our #1 priority. We welcome your comments and > suggestions about how we can improve the support we provide to you. Please > feel free to let my manager know what you think of the level of service > provided. You can send feedback directly to my manager at: > msdnmg(a)microsoft.com. >
From: Allen Chen [MSFT] on 8 Apr 2010 23:19 Hi Johan, >I'll do that. What seems weird is that the calls take longer than expected >and there is no locking in the database? >// Johan From your description you call database in your web service, which takes quite long time right? You may test the same logic in a Console application to see whether you get the same behavior. Some load tests for database would also be helpful to isolate the problem. If finally it turns out to be a database issue and you're using SQL Server I recommend you ask question in http://technet.microsoft.com/en-us/sqlserver/bb895986.aspx Regards, Allen Chen Microsoft Online Support Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com
From: Allen Chen [MSFT] on 19 Apr 2010 02:33
Hi Johan, Do you have any progress on this issue? Regards, Allen Chen Microsoft Online Support Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com |