Alik Levin's

Clarity, Technology, and Solving Problems | PracticeThis.com

Performance Sin - Chatty Database Access And Loops (Plus Another Free Performance Tool)

Performance Sin - Chatty Database Access And Loops (Plus Another Free Performance Tool)

  • Comments 8

Chatty database access is the surefire way for slow performance caused by  resources starvation that might  even lead to denial of service. Following is a real world case.

Customer

Service Unavailable message is consistently observed when there are more than 150 users access the web site. We think IIS cannot handle more than 150 users. What would you suggest?

Support

Let's see what "Service Unavailable" means. "IIS cannot start any new worker processes because of limited system resources...". Let's see the code.

The code

The code was calling on DB Access function that was put inside for loop that was called inside event handler. The event handler was called on each GridVew's row creation. Meaning, DB access in nested loop. In case of small GridVew of 10 rows and 10 cells the database would be accessed 100 times for each request. 150 concurrent users would create significant load of 15,000 connections:

image

SQL Server Profiler

After running SQL Server profiler it became clear that database access should be significantly improved. Following is the number of SQL Commands performed as a result of single request:

image

 

Conclusion

For improved performance avoid chatty data base access. Apply caching techniques instead.

More free performance tools

If you use SQL Server 2005 Express which does not come with built-in profiler you might find useful the following free tool:

Profiler for Microsoft SQL Server 2005 Express Edition

My related posts

  • You've been kicked (a good thing) - Trackback from DotNetKicks.com

  • Serving images dynamically may cause performance hit. Dynamically served images require more HTTP requests

  • Je viens de découvrir cet outil au détour d'un post d'Alik Levin . Comme son nom l'indique, son but est

  • Your ASP.NET application performs slower than expected? How many times do you access your database for

  •      To achieve best performance you need to make decisions based on trade-off between

  •     In my previous post -  Best ASP.NET Performance Winner For Data Binding - Hands

  • In my previous post - Best ASP.NET Performance Winner For Data Binding - Hands Up To Response.Write()

  • Field experience proves - the earlier performance is tackled in development lifecycle the better results

Page 1 of 1 (8 items)