Performance Measurement of .NET Code

Performance Measurement of .NET Code
In .NET we often come across scenarios where we need to find out how much time the code takes to execute, and find the exact location in the code where the performance is not good.
Especially when you are working customer facing applications like website or webservices.


Avoid Using DateTime
When I was new in development, I was using datetime most of the time. I was using the following code to check the execution time:
DateTime start<br />long totalMilliseconds<br />start = DateTime.Now;<br /> <br />//Code to be executed goes here<br />//...<br />//...<br /> <br />totalMilliseconds = start.Subtract(DateTime.Now).Milliseconds;<br /> <br />System.Diagnostics.Trace.WriteLine("Execution Time -" + totalMilliseconds);
          
The above code works fine but its not very accurate.
I was working on a project where I was using CLR Store proc in SQL Server 2008 to call a webservice. I put the above code around it to
find out the execution time. It was taking about 400ms to execute the code. But in when I found the execution time for the store proc itself
in t-sql, it was taking about 1.4 second. At that time I realised that using DateTime is not a reliable method to find the execution time.

Use Stopwatch
As an alternative to this, I found that the .NET Framework already has a Stopwatch which is more accurate than DateTime.
I replaced my code with stopwatch and it give me accurate execution time.

System.Diagnostics.Stopwatch timer;<br />long totalMilliseconds;<br /> <br />timer = new System.Diagnostics.Stopwatch();<br />timer.Start();<br />//Code to be executed goes here<br />//...<br />//...<br />timer.Stop();<br />totalMilliseconds = timer.ElapsedMilliseconds;<br />System.Diagnostics.Trace.WriteLine("Execution Time -" + totalMilliseconds);<br />


___________________________________________________________________
Mitul Patel
http://dot-net-solutions.blogspot.com/
http://www.omkarsolutions.com.au/
___________________________________________________________________

I recommend the following books to improve your code performance.

Splitting string with deliminator In SQL Server

During my work I came to a problem where I had to extract some numbers from a comma

separated list of numbers in TSQL 2008 (Sql Server).

I had to extract last seven numbers from a comma separated list of 14 numbers.

Just for the start I created a table function called ufn_Split.

This function takes two arguments:

1. Data

2. Deliminator

And it returns the split data in a tabular format.

Below is the function :

CREATE FUNCTION [dbo].[ufn_Split]<br /> (<br /> @Data NVARCHAR(2000),<br /> @SplitOn NVARCHAR(5)<br /> ) <br /> RETURNS @RtnValue TABLE <br /> (<br /> rID INT IDENTITY(1,1),<br /> DATA NVARCHAR(100)<br /> ) <br /> AS <br /> BEGIN <br /> WHILE (CHARINDEX(@SplitOn,@Data)>0)<br /> BEGIN<br /> INSERT <br /> @RtnValue (DATA)<br /> SELECT <br /> LTRIM(RTRIM(SUBSTRING(@Data, 1, CHARINDEX(@SplitOn, @Data) -1)))<br /> <br /> SET @Data = SUBSTRING(@Data,CHARINDEX(@SplitOn, @Data) + 1, LEN(@Data))<br /> END<br /> <br /> INSERT <br /> @RtnValue (DATA)<br /> SELECT <br /> LTRIM(RTRIM(@Data))<br /> <br /> RETURN<br /> END <br />

___________________________________________________________________

Mitul Patel

http://dot-net-solutions.blogspot.com/

http://www.omkarsolutions.com.au/

___________________________________________________________________

I recommend the following books to improve your T-SQL Skills.