Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Added a new API to provide memory information that GC records#17326

Merged
Maoni0 merged 1 commit into
dotnet:masterfrom
Maoni0:ml_value
Apr 2, 2018
Merged

Added a new API to provide memory information that GC records#17326
Maoni0 merged 1 commit into
dotnet:masterfrom
Maoni0:ml_value

Conversation

@Maoni0
Copy link
Copy Markdown
Member

@Maoni0 Maoni0 commented Mar 29, 2018

This is to be used by BCL for deciding when to trim memory usage in pooling
code.

is to be used by BCL for deciding when to trim memory usage in pooling
code
@Maoni0 Maoni0 requested review from davmason and sywhang March 29, 2018 21:25
@davmason
Copy link
Copy Markdown

Is this all that's necessary for the array pool work?

@Maoni0
Copy link
Copy Markdown
Member Author

Maoni0 commented Mar 29, 2018

@davmason yes. array pool is actually not using all the info 'cause it doesn't currently track the sizes in the pool. should it track that in the future it could use all the info. strictly speaking, I also checked in #17177 which helps with trimming for 32-bit processes that run on machines with more physical mem than VM but that's applicable to more than just array pool.

@danmoseley danmoseley closed this Mar 31, 2018
@danmoseley danmoseley reopened this Mar 31, 2018
@Maoni0 Maoni0 merged commit 2583ce9 into dotnet:master Apr 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants