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

Out of memory exception in JIT/Regression/JitBlue/DevDiv_255294 #8034

Closed
sandreenko opened this issue May 9, 2017 · 2 comments
Closed

Out of memory exception in JIT/Regression/JitBlue/DevDiv_255294 #8034

sandreenko opened this issue May 9, 2017 · 2 comments
Assignees
@BruceForstall
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI disabled-test The test is disabled in source code against the issue enhancement Product code improvement that does NOT require public API changes/additions JitThroughput CLR JIT issues regarding speed of JIT itself tenet-performance Performance related issue
Milestone
Future

Comments

@sandreenko
Copy link
Contributor

Crossgen mode uses full optimizations and has quadratic algorithm it terms of memory to build and keep reachability sets for blocks.
CoreRun mode was fixed in dotnet/coreclr#11233.
So now CoreRun needs 300Mb (was 3 GB), CrossGen needs 3GB (was 6 GB). And 3GB is too much for x86.
category:throughput
theme:large-methods
skill-level:intermediate
cost:medium
@BruceForstall BruceForstall changed the title [x86] Out of memory expection in JIT/Regression/JitBlue/DevDiv_255294 [x86] Out of memory exception in JIT/Regression/JitBlue/DevDiv_255294 May 9, 2017
@RussKeldorph RussKeldorph changed the title [x86] Out of memory exception in JIT/Regression/JitBlue/DevDiv_255294 Out of memory exception in JIT/Regression/JitBlue/DevDiv_255294 May 9, 2017
@RussKeldorph
Copy link
Contributor

I'm arguing that this isn't specific to x86...it's just that x86 is less able to accommodate this memory allocation pattern.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@BruceForstall BruceForstall added the JitUntriaged CLR JIT issues needing additional triage label Oct 28, 2020
@sandreenko sandreenko removed the JitUntriaged CLR JIT issues needing additional triage label Dec 30, 2020
@sandreenko sandreenko mentioned this issue Dec 30, 2020
Closed
@BruceForstall BruceForstall self-assigned this Aug 10, 2022
@BruceForstall BruceForstall mentioned this issue Aug 10, 2022
Closed
@BruceForstall
Copy link
Member

Closing this in favor of #44341

@ghost ghost locked as resolved and limited conversation to collaborators Sep 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@BruceForstall BruceForstall

Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI disabled-test The test is disabled in source code against the issue enhancement Product code improvement that does NOT require public API changes/additions JitThroughput CLR JIT issues regarding speed of JIT itself tenet-performance Performance related issue
Projects
None yet
Milestone
Future
Development

No branches or pull requests
4 participants
@msftgits @BruceForstall @RussKeldorph @sandreenko