Skip to main content

Immutable String and Performance

String of the type System.String is immutable in the .Net Framework. That means any change to a String causes the runtime to create a new string and abandon the
old one. Guess how many string references following code will create?

//c#
String s;

s= "one"; //"one"
s += " two"; //"one two"
s += " three"; //"one two three"
s += " four"; //"one two three four"
Console.WriteLine(s);

If you guessed it four, you are right. Most developers think this is only one string. After running the code only the last string has a reference, the other three are
disposed off during garbage collection. Avoiding these kind of temporary string helps avoiding unnecessary garbage collection and hence helps improve performance.

There are several ways to avoid temporary string

1. Use the Concat, Join or Format method of the String Class to join multiple items into a single statment.
2. Use StringBuilder Class to create dynamic(mutable) strings.

StringBuilder is most suitable solution as it can span multiple statments. Default buffer size is 18 bytes but you can specify the size as per your requirment. This buffer grows as needed.

//c#

System.Text.StringBuilder sb = new System.Text.StringBuilder(30);
sb.Append("one");
sb.Append(" two");
sb.Append(" three");
sb.Append(" four");
string s = sb.ToString(); //copy result to string
Console.WriteLine(s);

Comments

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0