fog-view poll timing #4005
Merged
fog-view poll timing #4005
Conversation
This file contains hidden or 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
|
|
|
|
joekottke
approved these changes
Sep 4, 2024
nick-mobilecoin
approved these changes
Sep 4, 2024
|
|
|
|
|
|
nick-mobilecoin
approved these changes
Sep 5, 2024
This was referenced Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Motivation
Make fog-view database polling interval configurable.
Before this change 1 view-store generated about 300 postgresql transactions/s in development.
After this change 1 view-store generated about 150 postgresql transactions/s in development.
Moving from default of 100ms to 250ms reduced number of transactions/s by just over half.
MC_DB_POLLING_INTERVAL_MSenv var for fog-view-storeFuture work
Investigate view queries. Look in to only doing update queries on stores with incomplete block ranges.