-
Notifications
You must be signed in to change notification settings - Fork 152
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
fog-view poll timing #4005
fog-view poll timing #4005
Conversation
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I'm not a Rust dev, this generally does make sense. But I'd rather have someone else confirm it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, some nits on naming and ownership logic
|
|
|
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_MS
env var for fog-view-storeFuture work
Investigate view queries. Look in to only doing update queries on stores with incomplete block ranges.