# express execution path > Depth-first rabbithole dossier for express execution path; source-anchored research pack. Parent: [MongoDB 8.0 performance changes & read-path regressions vs 7.0](https://llms-explorer.com/tree/mongodb-8-0-performance-changes-read-path-regressions-vs-7-0/) · 2 facets · 12 facts · page: https://llms-explorer.com/tree/express-execution-path/ ## Measurements and reference values - [medium] The Express path in MongoDB 8.0 can be extended to updates, deletes, and other unique index lookups, with dedicated C++ code using SortedDataInterface and RecordStore APIs providing at least a 10% performance win. Sources: https://www.mongodb.com/company/blog/engineering/mongodb-8-0-improving-performance-avoiding-regressions, https://jira.mongodb.org/browse/SERVER-81850 — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [low] Local testing with w:1, j:0 shows that using dedicated code for update by _id in the Express path yields a 10% end-to-end improvement, with larger gains expected for internal codepaths like oplog application. Sources: https://jira.mongodb.org/browse/SERVER-81850 — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [low] The Express path optimization was validated by a tiger team member's experiment to bypass the query planner and hard code reading from the storage engine, which delivered significant improvements to YCSB 100% read workloads. Sources: https://www.mongodb.com/company/blog/engineering/mongodb-8-0-improving-performance-avoiding-regressions — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#methodology` ## Facts and statements - [high] Starting in MongoDB 8.0, a limited set of queries, including `_id` equality matches, skip regular query planning and execution to use an optimized index scan plan called the Express path. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/manual/release-notes/8.0.md, https://www.mongodb.com/docs/manual/reference/explain-results.md, https://www.percona.com/blog/percona-server-for-mongodb-8-0-the-most-performant-ever/ — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [medium] The Express path in MongoDB 8.0 uses one of the following plan stages: `EXPRESS_CLUSTERED_IXSCAN`, `EXPRESS_DELETE`, `EXPRESS_IXSCAN`, or `EXPRESS_UPDATE`. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/manual/release-notes/8.0.md, https://www.mongodb.com/docs/manual/reference/explain-results.md — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [low] The Express path in MongoDB 8.0 is designed to support shard filtering only for unique, single-field indexes, as defined in SERVER-87016. Sources: https://jira.mongodb.org/browse/SERVER-97860 — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [low] The SERVER-81850 ticket proposes that the Express (aggressive IDHACK) path should also work for clustered collections, skipping the _id index and going directly to the record store. Sources: https://jira.mongodb.org/browse/SERVER-81850 — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [low] The Express path index selection algorithm finds an index suitable for the express equality path that satisfies the query with exact bounds and provably returns at most one result document, preferring the index with the fewest fields. Sources: https://raw.githubusercontent.com/mongodb/mongo/v8.0/src/mongo/db/query/plan_executor_express.h — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [high] A bug in MongoDB 8.0 allows the Express path to incorrectly use unique, multi-field indexes, which can return incorrect results as tracked in SERVER-97860. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/manual/release-notes/8.0.md, https://jira.mongodb.org/browse/SERVER-97860 — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#troubleshooting` - [low] To mitigate the Express path bug in MongoDB 8.0-8.0.4, users should upgrade to 8.0.6, add a hint() to the query, or set internalQueryDisableSingleFieldExpressExecutor to true to disable the fault path for non-_id queries. (verified as of 2026-10-15) Sources: https://jira.mongodb.org/browse/SERVER-97860 — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#troubleshooting` - [low] In MongoDB 8.0, find-by-_id operations using non-simple projections miss the Express executor, so default projections should be supported to avoid falling back on idhack. Sources: https://jira.mongodb.org/browse/SERVER-91825 — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` - [low] Starting in MongoDB 8.0, wiredTiger.concurrentTransactions is renamed to queues.execution. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/manual/release-notes/8.0-compatibility.md — source: `~/.global-ai-hub/research/.pipeline/mongodb-2026-10-14/frb/express-execution-path-ec9369fccf/rabbithole-synthesis.md#core` ## Related concepts - express — is a part of express execution path - path — is a part of express execution path - execution — is a part of express execution path