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

Load test Requests per second #210

Closed
ValarDragon opened this issue May 29, 2021 · 2 comments
Closed

Load test Requests per second #210

ValarDragon opened this issue May 29, 2021 · 2 comments

Comments

@ValarDragon
Copy link
Member

We need to find out how many requests per second a node can handle.

For now, we should probably make such a benchmark with

  • Getting all pools
  • Getting total liquidity
  • Calculating Rewards
  • spot price of a few pools

We can get a better profile of requests to run from @dogemos later.

There are some mutex locks in different places in the stack (e.g. tendermint/tendermint#6048, IAVL) which we should see if we can either fix, or skirt the need to use.

@tac0turtle
Copy link
Contributor

It seems like many of the requests you mention above are sdk related. I would love to test if we get any performance improvements by removing most of this code cosmos/cosmos-sdk#8549 in favor of setting a RWmutex in the sdk opposed to handing it off to tendermint.

This will for sure fix tendermint related query issues

@ValarDragon
Copy link
Member Author

100% agreed, this was mainly motivated because of the lack of concurrency.

However, I'm not at all convinced that the SDK isn't going to have weird locks elsewhere, e.g. every telemetry call making a mutex contention, even if telemetry isn't used on that ABCI connection!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants