Skip to content

op-acceptance-tests: interop: use different EOAs in load test #16044

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

Open
joshklop opened this issue May 21, 2025 · 0 comments · May be fixed by #16066
Open

op-acceptance-tests: interop: use different EOAs in load test #16044

joshklop opened this issue May 21, 2025 · 0 comments · May be fixed by #16066
Assignees
Labels
A-acceptance-tests C-load-testing go Pull requests that update Go code H-interop Hardfork: change planned for interop upgrade

Comments

@joshklop
Copy link
Contributor

joshklop commented May 21, 2025

The load test in #16032 uses the same EOAs to spam transactions. This could hit existing mempool DoS protections since op-geth op-geth limits the number of concurrent pending txs per account.

For the interop load test, we want to the interop implementation to be the limiting factor.

To resolve this, we should spam transactions from different EOAs, maybe even using a fresh EOA each time for simplicity.

@joshklop joshklop self-assigned this May 21, 2025
@joshklop joshklop added go Pull requests that update Go code H-isthmus Hardfork: change is planned for isthmus upgrade labels May 21, 2025
@tynes tynes added H-interop Hardfork: change planned for interop upgrade and removed H-isthmus Hardfork: change is planned for isthmus upgrade labels May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-acceptance-tests C-load-testing go Pull requests that update Go code H-interop Hardfork: change planned for interop upgrade
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

2 participants