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

High ram during compile of EF.Core Project #20032

Closed
yakeer opened this issue Feb 23, 2020 · 1 comment
Closed

High ram during compile of EF.Core Project #20032

yakeer opened this issue Feb 23, 2020 · 1 comment
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@yakeer
Copy link

yakeer commented Feb 23, 2020

Hello,
I have an EF core version 3.0.0 project,
With quite a large relational db context (around 200 entities).
The Migrations assembly is in the same project, with around 200 migrations (this is an ongoing project).

My issue is, that during build, the RAM of dotnet process (MacOS, but also happens in Windows Machine) is going up to 7GB.

Is this normal? am I doing something not according to Best Practice?

@ajcvickers
Copy link
Member

ajcvickers commented Feb 24, 2020

@yakeer There are of course many factors involved, but this does not seem abnormally high to me, especially when the build is automatically handled by multiple underlying processes.

With regard to the number of migrations, we do recognize this as an issue. We have ideas in this area such as being able to automatically squash migrations, and making it easy for migrations to be more separated from main application code.

Try the Roslyn repo if you want to follow up further on compiler memory use.

@ajcvickers ajcvickers added the closed-no-further-action The issue is closed and no further action is planned. label Feb 24, 2020
@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

2 participants