New Post: Query generation in batch insert scenarios

I have noticed that EF produces a large number of discrete insert statements when SaveChanges is called with a large number of new rows. It would be sensible here if instead of using individual INSERT INTO VALUE() statements a single INSERT INTO VALUES() statement was called.

In my test this has improved performance of regular SQL statements by a factor of about 8 or 9 and also performs much better in high latency scenarios. This is in-line with how SqlBulkCopy works in .net