[EF Core](https://github.com/dotnet/efcore) writes SQL so you don't have to. But when that SQL is slow, bloated, or just weird—how do you even know? Most developers never see what EF Core actually sends to the database. Time to change that. I built [EF Core Bench Lab](https://github.com/jernejk/efcore-bench-lab) after one too many times optimising queries locally, only to watch them fall apart in prod—different data, different execution plans, different problems. The tool intercepts queries and execution plans, turning the invisible visible. We'll use it to catch performance anti-patterns in the act, then hand the evidence to AI for rapid diagnosis. You'll see real examples of N+1s, cartesian products, and tracking traps—and why that index you added in dev made everything worse in prod. Peek inside the black box. You might be surprised what's in there. **Meetup kindly sponsored this month by our friends at ?**. 🍕 **Schedule (Brisbane/Australia GMT+10):** **5:00pm** Attendees can arrive in-person. **5:30pm** Refreshments. **6pm** Housekeeping & Intro. **6:05pm** Talk by JK (\~1 hour). **\~7:15pm** Close. **Live stream** from 6pm AEST via our [YouTube](https://www.youtube.com/channel/UCAAidDuk0U9jfnAz3njEizQ) channel. 📽️ **Recordings** after the event on our [YouTube](https://www.youtube.com/channel/UCAAidDuk0U9jfnAz3njEizQ) channel. 📺 **Venue** kindly sponsored by [Microsoft](https://www.microsoft.com/). 🪑 **Lucky door prizes** kindly sponsored by [JetBrains](https://www.jetbrains.com/). 📜 We are glad to recommend our sponsors products and services, and we appreciate their ongoing sponsorship of our user group! 😁