From 047cc2f39b7ddbf8c49b993f62cda26fba78f527 Mon Sep 17 00:00:00 2001 From: Shay Rojansky Date: Sun, 12 Apr 2026 20:23:21 +0200 Subject: [PATCH] Add some perf info to 11 what's new docs --- entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md b/entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md index 8048bb847a..8cc55a4d98 100644 --- a/entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md +++ b/entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md @@ -154,7 +154,9 @@ In EF Core 11, the redundant column is omitted: ORDER BY [b].[BlogId] ``` -Both optimizations can have a significant positive impact on query performance, especially when multiple reference navigations are included. +Both optimizations can have a significant positive impact on query performance, especially when multiple reference navigations are included. A simple, common split query scenario showed a **29% improvement in querying performance**, as the database no longer has to perform the to-one join; single queries are also significantly improved by the removal of the ORDER BY, even if a bit less: one scenario showed a **22% improvement**. + +More details on the benchmark are available [here](https://github.com/dotnet/efcore/issues/29182#issuecomment-4231140289), and as always, actual performance in your application will vary based on your schema, data and a variety of other factors. @@ -259,6 +261,8 @@ var embeddings = await context.Blogs Vector properties can still be used in `WHERE` and `ORDER BY` clauses—including with `VectorDistance()` and `VectorSearch()`—and EF will correctly include them in the SQL, just not in the entity projection. +This optimization can have a dramatic impact on application speed: a minimal benchmark showed an almost 9x (that's nine-fold) increase in performance, and that's while running against a local database. The optimization is even more impactful as latency to the database grows: when executing against a remote Azure SQL database, an improvement of around 22x was observed. More details on the benchmark are available [here](https://github.com/dotnet/efcore/issues/37279#issuecomment-4232243062), and as always, actual performance in your application will vary based on your entity, vector properties and latency. + ### Full-text search improvements