Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Performance: Implement DbContext pooling for high scale scenarios #6923

Closed
5 of 6 tasks
anpete opened this issue Nov 2, 2016 · 2 comments
Closed
5 of 6 tasks

Performance: Implement DbContext pooling for high scale scenarios #6923

anpete opened this issue Nov 2, 2016 · 2 comments
Assignees
@anpete
Labels
area-perf closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone
2.0.0

Comments

@anpete
Copy link
Contributor

anpete commented Nov 2, 2016 •
edited
Loading

  • Add overload of AddDbContext that enables pooling
  • OnConfiguring is never run. Configuration is external only.
  • Add state reset (context behavior flags, internal StateManager state)
  • Add Dispose event redirection.
  • Logging
  • Pool cleanup
@anpete anpete self-assigned this Nov 2, 2016
@anpete anpete added this to the 1.2.0 milestone Nov 2, 2016
anpete added a commit that referenced this issue Nov 5, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
8fa937c 
- Initial impl. of context pooling.
anpete added a commit that referenced this issue Nov 5, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
05a9497 
- Initial impl. of context pooling.
anpete added a commit that referenced this issue Nov 5, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
9d59b3d 
- Initial impl. of context pooling.
anpete added a commit that referenced this issue Nov 5, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
3fc2889 
- Initial impl. of context pooling.
anpete added a commit that referenced this issue Nov 5, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
fab7850 
- Initial impl. of context pooling.
anpete added a commit that referenced this issue Nov 8, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
b3f2b7c 
- Initial impl. of context pooling.
anpete added a commit that referenced this issue Nov 9, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
5577dda 
- Initial impl. of context pooling.
anpete added a commit that referenced this issue Nov 16, 2016
@anpete
PERF: Fix #6923 - Implement DbContext pooling for high scale scenarios.
72fe05b 
- Initial impl. of context pooling.
@anpete anpete closed this as completed in 4376b2d Nov 16, 2016
@divega divega added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label May 8, 2017
@ajcvickers ajcvickers changed the title PERF: Implement DbContext pooling for high scale scenarios Perf: Implement DbContext pooling for high scale scenarios May 9, 2017
@ajcvickers ajcvickers changed the title Perf: Implement DbContext pooling for high scale scenarios Performance: Implement DbContext pooling for high scale scenarios May 9, 2017
@bryan07
Copy link

bryan07 commented Jul 13, 2017

As OnConfiguring is never run, how is it possible to configure many different connectionstring at runtime using DbContext Pooling?

@ajcvickers
Copy link
Contributor

@bryan07 DbContext pooling uses the same context instances with the same configuration and hence has the limitation that you cannot change that configuration. This means that right now the connection string cannot be changed. It may be possible to do this once #8427 and/or #8494 are implemented, but I don't think we have thought deeply about whether this will play well with pooling.

@ajcvickers ajcvickers modified the milestones: 2.0.0-preview1, 2.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@anpete anpete

Labels
area-perf closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
4 participants
@anpete @divega @ajcvickers @bryan07