Optimizing Laravel eloquent performance for large datasets

we're running into a persistent challenge with `Laravel Quick Fix & Consultation` client projects, particularly when tackling `eloquent performance` bottlenecks in existing applications.

the core issue revolves around optimizing complex queries involving multiple relationships and large datasets, often beyond what simple eager loading can efficiently handle.

• Context: many clients have legacy Laravel apps with poorly optimized ORM usage.
• Problem: standard eager loading (`with()`) works for simple cases, but with deeply nested relations or conditional loads, it becomes unwieldy or still leads to N+1 in specific scenarios.
• Specific technical challenge: trying to build a generic "quick fix" for identifying and refactoring queries that are causing slowdowns, especially when aggregate functions or complex `whereHas`/`whereDoesntHave` clauses are involved. raw SQL is always an option, but we want to stick to Eloquent as much as possible for maintainability.
• Question: what advanced patterns or packages do you use to diagnose and optimize `eloquent performance` for very large datasets and intricate relationships without resorting to full raw SQL rewrites? specifically looking for strategies beyond basic `with()` and `select()` calls.