5 Tips to Improve Performance of C# Code

Nice article

Your example is wrong in foreach, You are accessing the element from a list in second case however in the first one you are using a number directly.

Nice article

Taking any of these recommendations as gospel is a good way to screw yourself over. As a rule of thumb you are not smarter than the compiler. If you think you might have found an edge case where the compiler is not doing what it's supposed to do and you can do better, you need to benchmark that specific piece of code. And not be a bonehead by doing it in debug mode.

Nice article

Any one have idea where create class object we can create global or in method

That great

Not of it is correct either.

ALL, is wrong ALL is bullshit, you no idea what you doing. U second and 3rd are wrong from beginning you messure, is order of magnitude to big. Struck are NOT be general they are only better in few specific areas, in many cases they are slower than class. foreach is only few % slower than for, not 2 times. + operator is faster than stringBuldier if u add less than 4 elements. 1 is good because knowing structure make difference but u dont know array list is implemented and u did test wrong. If you init list size in costructor like you did in array it will be only few % slower. 5 will be optim ;), but in general case is faster.

Tip 5 is wrong, this is because you ran from the VS debugger. The compiler doesn't optimise when run from the debugger. If you run the exe outside Visual Studio and add a warmup loop at the start so that the JIT has time to work as well you get these results:warmup: 4Direct Assign: 1 Using Property: 1

Very nice

very very good article.

good one

Good article.

Thanks for pretty good article. but for #Tip4, string is much faster then string Builder...

Well,i will follow from today

For Tip#1 - The slow performance is NOT because List<int> stores it in object format but the Array.Copy, I think. Since you defines it as List<int>, it should store it in int format but object. That is to say, there is no additional boxing/unboxing operations.

Sir,This article is very good for begginers just like me.You discussed about time taking by for loop and foreach loop.You write that for loop is faster then Foreach loop.But accrording me it not always true it depend upon data type which you using. like for "Array" Foreach is faster Then For loop and for "List" For loop is faster then faster then Foreach

You're right eric... accessing the array each time would then push down performance very much... look at this for greater understanding what to use: http://www.dotnetperls.com/for-foreach

In Tip #2, inside the for loop should be lst1.Add(Count[i]); instead of lst1.Add(i);. This would get the values from the Count list similar to what the foreach loop does. The Article Extension has this same problem.

I usually prefer using For for high performance code :)

Hi Sourav, Thanks for pretty good article. Can you please explain why did you choosed a low number of itterations for measuring performance? for example i did raised the itterations on tip#5 to 1000000000 (1e9) from 100, and then the performance of assigning property and field was very near (~%25 difference). And can you explain the reason of this difference?

Thanks for providing such a nice information.

good one keep it up

very good, thank you. but i think we shuld test property after it be used tirst time. because ,first time to user property(no matter get or set ) will cost more time .

thanks for sharing

kudos for the article.depicts good practices.one should really follow

Very Impresive...

Good Post. Examples are good and easy to understand.

Reverse for loop(max count to 0) is fastest then foreach and for loop

really nice!

i am not sure Foreach is better that For loop , which version of C# you have tested, Can we try with some other collection types also

Very good sir, congratulations!

nice post and it is very informative

very good thought sir

Nice article

Great Tips..Very Helpful not only for Beginners but all developers........

Very very informative...

Nice Article and Very useful Thanks

Dear Sandeep ,you are correct . Thanks to share this information with us.

Dear Sam, I am not saying that string is less efficient or bad . Just i have tried to show in which situation ,what need to use. And if we choose perfect option in perfect situation then only performance will increase.

Nice article, Thanks Sourav!! Struct is a better than class because it is value type and no need boxing. But the size of struct is the sum of the sizes of its members and we define more members in struct then it will be get large. Then It will be create a problem and involved overhead when we passing its instance. Microsoft recommends that the size of a struct should ideally be below 16 bytes, but it really is up. So struct should use for lightweight objects not instead of class.

I agree that use of StringBuilder should be balanced with other criteria. I think one important point is that people that review other people's code should not automatically say that the string class is inefficient. The efficiency of the developer needs to be considered too. Note that the StringBuilder class does not have all the methods that the string class does. I do not understand why. I think that if the string class is not efficient then Microsoft needs to put all the methods that are in the string class in the StringBuilder class also.

Yes Sir, If there is huge string concatenation operation in development scenario then StringBuilder performs well.

I've added an Article Extension. So if there are only a few operations on strings, StringBuilder may not be a good idea.

Thanks Mahesh Sir,

Dear Akella, 5 th test i again tested in Release mode and without attached debugger and there is no change in performance :)

Welcome to C# Corner Saurav and great tips. Keep it up.

Very useful tips Thanks

Great Start, Welcome to the C# Corner.

in fifth test just change configuration to Release and run without attached debuger, you'l see the difference

structure allocates memmory much faster than reference type (because stack and heap), but you can face with performance problem when needs to copying value types

in first test change "new List<int>()" to "new List<int>(10000)" and run in Release w/o attached debugger

running tests in debug configuration is unaccpetable

very useful

Nice Article :) Thanks It Helped A Lot !!