Change cache hit ratio to reflect change since last snap #273
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
|
@Krysztophe : can you try this ? |
blogh
force-pushed
the
cache_hit_ratio
branch
from
c32ae93
to
73eca08
Compare
|
As said in private: with a pgbench scale 1000 (about the size of the 12 Gb share buffers), after a server restart, I get immediately a hit ratio around 65%-90%, although only a very small part of the tables are in the SB (checked with pg_buffercache) ?!? |
|
I tried with scale 300 (4GB) and the default shared buffers (128MB). |
blogh
force-pushed
the
cache_hit_ratio
branch
4 times, most recently
from
92e91aa
to
f074d9d
Compare
dlax
reviewed
Jun 10, 2022
dlax
requested changes
Jun 10, 2022
|
I have regened the man file and squashed the commits. |
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.
This fixes #272