Provide opt-in way to disable snapshotting/resetting for DbContext pooling

Open
#24,769 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
database, performance

Research direction

Start by tracing the DbContext pooling implementation and its existing reset behavior; the issue does not name specific files or tests. Compare the proposed opt-in behavior with Npgsql's “No Reset On Close” concept, and consider the 1.8% performance result as the success criterion.

Written by the indexing model from the issue text.

Description

area-dbcontext area-perf

Instead of using the built-in context pooling, I experimented with a non-resetting context pool which simply hands out instances without any state resetting etc.; this yielded a 1.8% perf increase. We can add an opt-in flag to DbContext pooling that would likely get use close to that.

Note similarity with Npgsql's No Reset On Close, which does the same at the ADO connection pooling level.

Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.