What is a common mistake with ExecuteUpdate and ExecuteDelete in Entity Framework Core?

Loading thousands of entities, changing them one by one, and calling SaveChanges creates unnecessary memory and statement overhead.