How does LINQ affect database write performance under bulk operations?

LINQ-based ORM writes are inefficient for bulk operations due to per-entity tracking overhead.

EF Core tracks entity state changes individually, meaning each insert/update/delete generates separate commands. LINQ does not batch writes natively. This leads to performance bottlenecks in bulk operations. Bulk libraries or raw SQL are preferred for high-volume writes. Change tracking and identity resolution add additional overhead.