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.

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

EF Core Compiled Model cache expiration #25188

Closed
sherazakbar50 opened this issue Jul 2, 2021 · 2 comments
Closed

EF Core Compiled Model cache expiration #25188

sherazakbar50 opened this issue Jul 2, 2021 · 2 comments
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@sherazakbar50
Copy link

Hi, For the first cold query ef core compiles the entire model that usually have a high cost propotional to the model size and complexity. Can this cache be invalidated when there is no request to the server and no query is executed for 20 minutes or so using dbcontext?

@roji
Copy link
Member

roji commented Jul 3, 2021

@sherazakbar50 the point of the new compiled model feature coming in EF 6.0 (#1906) is to reduce the first startup time, when your application first loads; the compiled model is generated via an explicit command, typically performed at design-time (or CI). Since a model cannot typically be changed after startup, I'm not sure what sense there would be in rebuilding it after inactivity... Can you provide more context on exactly what you're looking for?

@ajcvickers
Copy link
Contributor

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.

BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

@ajcvickers ajcvickers added the closed-no-further-action The issue is closed and no further action is planned. label Jul 11, 2021
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported
Projects
None yet
Development

No branches or pull requests

3 participants