-
Notifications
You must be signed in to change notification settings - Fork 34
feat: run stress test on PRs #434
Comments
Could you elaborate on this? |
👍 I updated the title and added a description. |
Can we create a |
I don't have any particular preference atm. I imagine that whoever picks this work can assess. I think the minimum requirement should be that the whole flow (querying indexer, requesting from node) is tested. |
not about preference, whether we decide to do a full benchmark crate to do all of this or are we benchmarking a specific crate. |
It would be useful to be able to run a stress test for the gateway on command.
Suggestion:
Consider that we should run all participants (indexer, node, gateway) locally in test so that latency (due to its volatility) does not affect the results.
The text was updated successfully, but these errors were encountered: