Skip to content
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

Implement test for global congestion control #9227

Closed
aborg-dev opened this issue Jun 20, 2023 · 1 comment
Closed

Implement test for global congestion control #9227

aborg-dev opened this issue Jun 20, 2023 · 1 comment
Labels
A-congestion Work aimed at ensuring good system performance under congestion

Comments

@aborg-dev
Copy link
Contributor

This is a continuation of work in #8920

We want a test case that will evaluate congestion in a multi-shard environment.
The main difference from the local congestion control is that the load that results in the congestion will be coming from other shards to the hot shard as incoming receipts.

We will reuse the same Locust setup, extending the workload defined in https://github.com/near/nearcore/blob/a5ede1d1cd54906ac91cbb614028b5323ddee0c0/pytest/tests/loadtest/locust/common/congestion.py.

The test should check that after a bursty load that is over the capacity of all shards, the transactions are properly queued up and eventually executed.

A good starting point will be reusing ComputeSum transaction, but issuing the requests to it from accounts on different shards.

@aborg-dev aborg-dev added the A-congestion Work aimed at ensuring good system performance under congestion label Jun 20, 2023
@aborg-dev aborg-dev self-assigned this Jul 14, 2023
@aborg-dev aborg-dev removed their assignment Sep 12, 2023
@aborg-dev
Copy link
Contributor Author

This work is superseded with near/NEPs#539.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-congestion Work aimed at ensuring good system performance under congestion
Projects
None yet
Development

No branches or pull requests

1 participant