Entity Framework DetectChanges Discover Why it is Slow

Why Entity Framework DetectChanges is slow?

More entities your context own, slower the DetectChanges method become!

Entity Framework does a great job detect all changes for us, but in exchange, we pay the high-performance cost!

Scenario:

Let look at this simple example to check the time taken when adding a different number of records, such as 1 record, 10, 100, 10000 records, etc.

using (var ctx = new EF6.CustomerContext())
{
	for(int i = 0; i < lines.Count; i++)
	{
		ctx.Customers.Add(customer);
	}
}

Imagine the Add method is called every time you add a new entity.

Performance Comparisons

Note:

• *: SaveChanges time not included
• **: Entity with two relations

OMG! 3h to add 100,000 records to a list? 210 ms to add a single record once we reach 100,000 records and we didn't have saved them yet in the database.

That's very common on Stack Overflow someone asks why his importation take over 10h. Only by using AddRange over Add, they usually save more than 2h.