increase parallelism

[CapCap]

Motivation

(Write your motivation for proposed changes here.)

Have you read the Contributing Guidelines on pull requests?

(Write your answer here.)

Test Plan

(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)

Related PRs

(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/aptos-labs/aptos-core/tree/main/developer-docs-site, and link to your PR here.)

If targeting a release branch, please fill the below out as well

• Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
• Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
• Why we must have it for V1 launch.
• What workarounds and alternative we have if we do not push the PR.

[netlify]

✔️ Deploy Preview for aptos-developer-docs canceled.

🔨 Explore the source changes: 9d77ee0

🔍 Inspect the deploy log: https://app.netlify.com/sites/aptos-developer-docs/deploys/623018b0772f3f0008dd0544

[aptos-bot]

❗ Invalid command

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.

General

• This project's Merge Queue can be found here.
• This project requires PRs to be Reviewed and Approved before they can be queued for merging.
• Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands

Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command	Action	Description
Land	land, merge	attempt to land or merge a PR
Canary	canary, try	canary a PR by performing all checks without merging
Cancel	cancel, stop	stop an in-progress land
Cherry Pick	cherry-pick <target>	cherry-pick a PR into <target> branch
Priority	priority	set the priority level for a PR (high, normal, low)
Help	help, h	show this help message

Options

Options for Pull Requests are configured through the application of labels.

Option	Description
	Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.
	Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.
	Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

[CapCap]

/canary

[aptos-bot]

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/4113
Forge Test Result: all up : 2057 TPS, 2130 ms latency, 3100 ms p99 latency,no expired txns

[aptos-bot]

💔 Test Failed - build-test-deploy