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

make pool_live_bytes metric more accurate #52015

Merged
merged 1 commit into from
Nov 4, 2023
Merged

Conversation

d-netto
Copy link
Member

@d-netto d-netto commented Nov 3, 2023

pool_live_bytes was previously lazily updated during the GC, meaning it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.

@d-netto d-netto requested a review from gbaraldi November 3, 2023 15:25
@d-netto d-netto added the GC Garbage collector label Nov 3, 2023
@vtjnash vtjnash added the merge me PR is reviewed. Merge when all tests are passing label Nov 3, 2023
@vtjnash vtjnash merged commit bc0d888 into master Nov 4, 2023
4 of 7 checks passed
@vtjnash vtjnash deleted the dcn-pool-live-bytes branch November 4, 2023 13:23
@giordano giordano removed the merge me PR is reviewed. Merge when all tests are passing label Nov 7, 2023
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request Nov 16, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
kpamnany pushed a commit to RelationalAI/julia that referenced this pull request Nov 16, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
d-netto added a commit to RelationalAI/julia that referenced this pull request Nov 28, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Nov 29, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 3, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 4, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 13, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 17, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 18, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 19, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 23, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 24, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 25, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Dec 26, 2023
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 6, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
Drvi pushed a commit to RelationalAI/julia that referenced this pull request Jan 8, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 13, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 14, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 15, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 17, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 18, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 23, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 24, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 25, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 27, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 30, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Jan 31, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Feb 1, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Feb 6, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Feb 7, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Feb 14, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Feb 21, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Feb 22, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
Drvi pushed a commit to RelationalAI/julia that referenced this pull request Feb 28, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Mar 1, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Mar 13, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
d-netto added a commit that referenced this pull request Mar 16, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
Drvi pushed a commit to RelationalAI/julia that referenced this pull request Apr 3, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
d-netto added a commit to RelationalAI/julia that referenced this pull request Apr 16, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Apr 23, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Apr 24, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Apr 30, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request Apr 30, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request May 2, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request May 9, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request May 19, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request May 26, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request May 28, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
DelveCI pushed a commit to RelationalAI/julia that referenced this pull request May 29, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
Drvi pushed a commit to RelationalAI/julia that referenced this pull request Jun 7, 2024
`pool_live_bytes` was previously lazily updated during the GC, meaning
it was only accurate right after a GC.

Make this metric accurate if gathered after a GC has happened.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GC Garbage collector
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants