This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Make subjective_cpu_leeway a config option - 1.8 #8027
Merged
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
…e_cpu_leeway_us to 31ms
larryk85
reviewed
Oct 3, 2019
larryk85
reviewed
Oct 3, 2019
larryk85
approved these changes
Oct 4, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Change Description
config.iniand command line option forsubjective_cpu_leewayproducer_api_pluginupdate_runtime_optionsConsensus Changes
API Changes
Documentation Additions
subjective-cpu-leeway-usdefaults to 31000us"Time in microseconds allowed for a transaction that starts with insufficient CPU quota to complete and cover its CPU usage."