C# Object Constructor Vs Initializer Syntax Performance Difference Tested

When it comes to code readability, the initialiser syntax makes declaring C# objects very easy and clean to read. It also makes writing the code much faster since you do not need to be adding new constructors and lets you see what properties you have left to assign. But what about performance? Is one method faster than the other? I created some tests to see if the object constructor vs initializer syntax performance is difference is noticeable, here are the results.

To test this I created a console app with a stopwatch that would check to see the amount of time taken to declare an object using a standard constructor and time to declare using the object initializer syntax, aka using curly braces to declare an object.

I used the following code to do this.

	class Program
		static void Main(string[] args)
			var descriptiuon = "Longer description string for testing to see which type of object declaration method is the fastest.";
			var stopwatch = Stopwatch.StartNew();
			var test1 = new TestObject
				ID = 1,
				Name = "test",
				Description = descriptiuon,
				Created = DateTime.Now,
				Updated = DateTime.Now,
				Number = 123456789012,
				Email = "[email protected]"
			Console.WriteLine($"Test 1: {stopwatch.ElapsedMilliseconds}ms");
			var test2 = new TestObject(1, "test2", descriptiuon, DateTime.Now, DateTime.Now, 123456789012, "[email protected]");
			Console.WriteLine($"Test 2: {stopwatch.ElapsedMilliseconds}ms");

	public class TestObject
		public TestObject()


		public TestObject(int id, string name, string description, DateTime created, DateTime updated, long number, string email)
			ID = id;
			Name = name;
			Description = description;
			Created = created;
			Updated = updated;
			Number = number;
			Email = email;

		public int ID { get; set; }
		public string Name { get; set; }
		public string Description { get; set; }
		public DateTime Created { get; set; }
		public DateTime Updated { get; set; }
		public long Number { get; set; }
		public string Email { get; set; }

I ran the console app using Visual Studio 2017 and the result was a little surprising. 5ms might not seem like a lot to some, but when you are dealing with some code that does this millions of times, this is a big difference. I ran it a few more times and It varied between 2ms-5ms.

I wondered if this was just down to the order in which they were run and not to do with the method used. So I switched the tests around so that Test 2 would run first. If this tool 0ms and the other still took 5ms, then it would be a solid conclusion that using object constructors are faster than using the initializer syntax.

With the methods switched around, it shows that it doesn’t matter which method is used, it is the first one that takes the longest. After this point, all further declarations are instant. To be fully sure of this, I added a for loop that would run this code 100 times. Here is the output.

As you can see, the first call took 2ms and all subsequent calls were instant. At this point it is safe to say that both methods of declaring objects in C# are equally as fast. There is no benefit to using a constructor to declare your objects. Since it takes longer to write code this way, it is best to use the object initializer syntax when writing code.

Related Articles

Related Questions

Function Keys Reversing Between Fn Actions And Normal

My keyboard has the usual F1 to F12 keys along the top. I use these for shortcuts in various applications. These keys also have...

Whirlpool Oven F6E6: Appliance Manager 1 Board Communication

I have a brand new Whirlpool oven W11I OM1 4MS2 H or (859991549450). I bought it alongside the microwave combi oven. I have had...

Whats the difference between the Tapo P100 and the P105?

There are a few different Tapo smart plugs. The P100 and P110 differ based on the smart power monitoring feature but where does the...


  1. This makes complete sense. With the object initializer you are assigning values to individual properties, which is far more calls than assigning multiple properties via a constructor. This is especially important if you’re assigning properties in an object in another layer.

  2. Nice. I thought the compiler would optimise the code anyway, wether using the initialiser syntax or not. Though I agree that the initialiser syntax is more readable, the debugging experience is not that great.


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Latest Tools

Memory Converter

Converting values between various metric measurements is usually quite simple as there will be 1000 of the smaller unit in the next larger unit....

Bitrate Converter

Below you will find a bitrate converter. This tool will allow you to enter a bitrate value, in one of many different formats and...

Aesthetic Text Generator

There are various ways to make your social media profile seem more unique, some of which are not as easy to implement as others....

Aspect Ratio Calculator For Images

Aspect ratio is the ratio between the height and width of an image. If you want to resize an image by 100 pixels, you...

Add Text To Image

Use this free tool to add text to an image. Simply select the image file that you want to overlay text onto and you...

JavaScript Multi-line String Builder

Javascript did not always support multi-line strings. If you attempted to create a string variable using quotes, putting a line break into the source...

Latest Posts

Latest Questions