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

Benchmarking #19

Open
Tracked by #126
sideninja opened this issue Jan 12, 2024 · 3 comments
Open
Tracked by #126

Benchmarking #19

sideninja opened this issue Jan 12, 2024 · 3 comments
Assignees
Milestone

Comments

@sideninja
Copy link
Contributor

sideninja commented Jan 12, 2024

Implement benchmarking tests for event indexing to gauge scalability of the solution.
The more concerning aspect of the scalability is query access of the storage as the size of the data grows. The aspect of keeping up with the events emitted related to EVM execution is not concerning.

We should also implement loaders that test the whole system on the benchmarking network (benchnet) which would be part of e2e testing.

@m-Peter
Copy link
Collaborator

m-Peter commented Feb 7, 2024

A tool worth trying out for benchmark & load testing is https://www.paradigm.xyz/2023/06/flood

@j1010001 j1010001 changed the title Benchmarking and e2e testing Benchmarking Feb 8, 2024
@sideninja
Copy link
Contributor Author

Let's start benchmarking using the flood tool https://github.com/paradigmxyz/flood

@m-Peter can you take this on and share here suggested strategy to benchmark and to stress-test.

Start by running everything against local emulator and EVM GW. After the test also inspect the output logs for any potential issues during the tests (unknown bugs).

@m-Peter
Copy link
Collaborator

m-Peter commented Aug 20, 2024

@sideninja Sure thing 👍 I will get started on this, to get a feel of how it works and whether it works for our use-case, and will then share the findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants