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.
Running the load test with 500x1 upkeeps encountered a strange issue after running for ~25 minutes:
@anirudhwarrier tried adjusting the number of keys and increasing the gas limit, but this only offset when this issue occurred
Additionally, we observed that after a few minutes, the number of transactions per block had doubled beyond what was expected based on previous runs, e.g. the previous runs looked like:
Whereas with lookbackBlocks set to 100, we saw this:
Going back over the latest develop merges, the culprit was my PR for dequeuing minimum number of logs
The 500x1 test had ran successfully on the feature branch, but not after we changed the lookback blocks from 128 to 100
This PR reverts that one change, and the 500x1 load test now runs without this issue, though I'm not sure yet why it caused this issue