Performance logging tips
        Posted  
        
            by Germstorm
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by Germstorm
        
        
        
        Published on 2010-03-23T19:57:13Z
        Indexed on 
            2010/03/23
            20:33 UTC
        
        
        Read the original article
        Hit count: 404
        
I am developing large data collecting ASP.Net/Windows service application-pair that uses Microsoft SQL Server 2005 through LINQ2Sql. Performance is always the issue.
Currently the application is divided into multiple larger processing parts, each logging the duration of their work. This is not detailed and does not help us with anything. It would be nice to have some database tables that contain statistics that the application itself collected from its own behavior.
What logging tips and data structures do you recommend to spot the parts that cause performance problems?
© Stack Overflow or respective owner