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

Recycle ADO.NET objects in update pipeline #15546

Open
Tracked by #28479
roji opened this issue May 1, 2019 · 1 comment
Open
Tracked by #28479

Recycle ADO.NET objects in update pipeline #15546

roji opened this issue May 1, 2019 · 1 comment
Assignees
@roji
Labels
area-perf punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. type-enhancement
Milestone
Backlog

Comments

@roji
Copy link
Member

roji commented May 1, 2019

There's a potential to reduce allocations by internally recycling DbParameter, DbCommand, and DbConnection instances - this should be a relatively low hanging fruit.

Am creating this issue to remember this possible avenue, but we should first do a proper memory profiling session and identify the biggest offenders first (ADO.NET may not be high on the list).
@roji roji added the area-perf label May 1, 2019
@ajcvickers ajcvickers added this to the Backlog milestone May 3, 2019
@roji roji changed the title Investigate potential recycling of ADO.NET objects Recycle ADO.NET objects in update pipeline Oct 20, 2021
@ajcvickers ajcvickers modified the milestones: Backlog, 7.0.0 Oct 22, 2021
@ajcvickers ajcvickers added propose-punt punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. and removed propose-punt labels Apr 22, 2022
@ajcvickers ajcvickers modified the milestones: 7.0.0, Backlog Apr 23, 2022
@AndriySvyryd
Copy link
Member

Related to #11574

@AndriySvyryd AndriySvyryd mentioned this issue Oct 18, 2023
Open
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@roji roji

Labels
area-perf punted-for-7.0 Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints. type-enhancement
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@ajcvickers @roji @AndriySvyryd