Skip to content

Add closure resolution benchmark#179

Merged
PhenX merged 1 commit intomasterfrom
feature/closure-benchmark
Mar 12, 2026
Merged

Add closure resolution benchmark#179
PhenX merged 1 commit intomasterfrom
feature/closure-benchmark

Conversation

@PhenX
Copy link
Collaborator

@PhenX PhenX commented Mar 12, 2026

No description provided.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new BenchmarkDotNet benchmark to measure closure-capture overhead paths relevant to ProjectableExpressionReplacer.VisitMember, helping quantify costs of captured value fields vs captured subquery inlining within EF Core query translation.

Changes:

  • Introduces ClosureCaptureBenchmark with two closure-capture scenarios (value closure + subquery closure) across baseline/full/limited modes.
  • Adds “isolated” benchmarks that call ProjectableExpressionReplacer.Replace() directly to reduce EF Core pipeline noise.

@PhenX PhenX merged commit eb618fe into master Mar 12, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants