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 is a stop-gap. For whatever reason, we aren't replaying log entries any faster than one entry per tick. This makes replaying the log be about 15x slower than loading the data initially cost (when running locally on a Thinkpad W520). So, reducing the tick interval by a factor of 20 seems like it'll make the Raft tick frequency not be the bottleneck.
In general this won't be true, for example, if we did the initial writes more slowly, then they'd likewise be forwarded to other nodes more slowly (with fewer writes per raft index). This generally doesn't fix the overall problem.
Connected to #1180.
This change is