Skip to content

Update COR_PRF_GC_GENERATION #18056

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

Merged
merged 5 commits into from
Apr 24, 2020
Merged

Update COR_PRF_GC_GENERATION #18056

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f64d5df
update COR_PRF_GC_GENERATION
davmason Apr 24, 2020
85bc6bc
actually add the changes
davmason Apr 24, 2020
43c634e
Apply suggestions from code review
davmason Apr 24, 2020
53f24da
add space to satisfy linter
davmason Apr 24, 2020
d0453cf
Update docs/framework/unmanaged-api/profiling/cor-prf-gc-generation-e…
davmason Apr 24, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/framework/unmanaged-api/profiling/cor-prf-gc-generation-enumeration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,8 @@ typedef enum {
COR_PRF_GC_GEN_0 = 0,
COR_PRF_GC_GEN_1 = 1,
COR_PRF_GC_GEN_2 = 2,
COR_PRF_GC_LARGE_OBJECT_HEAP = 3
COR_PRF_GC_LARGE_OBJECT_HEAP = 3,
COR_PRF_GC_PINNED_OBJECT_HEAP= 4
} COR_PRF_GC_GENERATION;
```

Expand All @@ -37,9 +38,12 @@ typedef enum {
|`COR_PRF_GC_GEN_1`|The object is stored as generation 1.|
|`COR_PRF_GC_GEN_2`|The object is stored as generation 2.|
|`COR_PRF_GC_LARGE_OBJECT_HEAP`|The object is stored in the large-object heap.|
|`COR_PRF_GC_PINNED_OBJECT_HEAP`|The object is stored in the pinned-object heap.|

## Remarks
The garbage collector improves memory management performance by dividing objects into generations based on age. The garbage collector currently uses three generations, numbered 0, 1, and 2, plus a special heap segment that is used for large objects. Objects whose size is larger than a particular value are stored in the large-object heap. Other allocated objects start out belonging to generation 0. All objects that exist after garbage collection occurs in generation 0 are promoted to generation 1. Objects that exist after garbage collection occurs in generation 1 move into generation 2.
The garbage collector improves memory management performance by dividing objects into generations based on age. The garbage collector currently uses three generations, numbered 0, 1, and 2, and two special heap segments, one for large objects and one for pinned objects.

Objects whose size is larger than a threshold value are stored in the large-object heap. Pinned objects can be allocated to the pinned-object heap to avoid the performance cost of allocating them on the normal heaps. Other allocated objects start out belonging to generation 0. All objects that exist after garbage collection occurs in generation 0 are promoted to generation 1. Objects that exist after garbage collection occurs in generation 1 move into generation 2.

The use of generations means that the garbage collector has to work with only a subset of the allocated objects at any one time.

Expand Down