I will optimize your slow dotnet API and ef core sql queries


About this gig
Is your .NET / ASP.NET Core API slow endpoints taking seconds, EF Core queries hammering SQL Server? I fix that, and prove it with before/after benchmarks.
I'm a senior .NET engineer with 11+ years building and optimizing production APIs. I recently took a search endpoint from multi-second to sub-300ms by pushing filters into the database and cutting projection over-fetch. I bring that same discipline to your code.
What I do:
Profile your slow endpoints and queries to find the real bottleneck
Fix N+1 queries, over-fetching, missing AsNoTracking, and bad LINQ translations
Push filtering and paging into SQL / Cosmos instead of memory
Tune EF Core, add the right indexes, and fix async misuse
Deliver clear before/after benchmarks so you see the gain
Stack: C#, ASP.NET Core, EF Core, SQL Server, Azure, Cosmos DB, Dapper.
Every change comes with measurements no hand-waving. Send me your slow endpoint or repo and I'll tell you honestly what's fixable and how much faster it can get.
Get to know Ahmed L
Senior dotNet and Azure Developer
- FromMorocco
- Member sinceJul 2026
Languages
English, Arabic, French
Other Software Development Services I Offer
FAQ
What do you need from me to get started?
Access to the slow endpoint or repo, the current response times, and a way to reproduce the load. Read-only DB access helps me diagnose; dev/test write access lets me implement the fixes.
Will you implement the fixes or just tell me what's wrong?
Both, depending on the package. Basic delivers a diagnosis and fix plan with benchmarks; Standard and Premium implement the fixes and re-measure so you see the real gain.
Do you provide before and after proof?
Always. Every optimization ships with before/after benchmarks — response time, RU/s or query cost — so the gain is measured, never just claimed.
