-
-
Notifications
You must be signed in to change notification settings - Fork 971
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
Survived Memory #1596
Open
timcassell
wants to merge
2
commits into
dotnet:master
Choose a base branch
from
timcassell:survivedMemory
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Survived Memory #1596
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timcassell
force-pushed
the
survivedMemory
branch
6 times, most recently
from
November 30, 2020 01:01
c88f7bf
to
db259cd
Compare
.NET Core 3.1 and 5.0 measurement issue: dotnet/runtime#45446 |
timcassell
force-pushed
the
survivedMemory
branch
from
December 5, 2020 04:20
82ec67e
to
fa943b3
Compare
timcassell
force-pushed
the
survivedMemory
branch
5 times, most recently
from
December 14, 2020 15:11
3e88680
to
116b4e0
Compare
timcassell
force-pushed
the
survivedMemory
branch
from
January 24, 2021 04:17
cac6356
to
b3f2aaf
Compare
Looks like measurement errors are fixed in .Net 7 as of dotnet/runtime#67160. |
timcassell
force-pushed
the
survivedMemory
branch
from
October 27, 2022 01:13
16a0665
to
5a9f217
Compare
timcassell
force-pushed
the
survivedMemory
branch
from
November 8, 2022 14:00
5a9f217
to
a51fe70
Compare
timcassell
force-pushed
the
survivedMemory
branch
2 times, most recently
from
March 18, 2024 06:54
51d25f1
to
73fffb5
Compare
timcassell
force-pushed
the
survivedMemory
branch
3 times, most recently
from
March 18, 2024 09:14
7b8667d
to
91027de
Compare
…rst benchmark run.
timcassell
force-pushed
the
survivedMemory
branch
from
March 18, 2024 09:25
91027de
to
0d6500f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In an attempt to address my question on #1579, I worked on this.
I added an optional
includeSurvived
flag onMemoryDiagnoserAttribute
and--memorySurvived
command line option to capture the survived memory from a benchmark run.