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

Testnet Stress Tests #341

Closed
timbeiko opened this issue Jun 18, 2021 · 3 comments
Closed

Testnet Stress Tests #341

timbeiko opened this issue Jun 18, 2021 · 3 comments

Comments

@timbeiko
Copy link
Collaborator

When London is live on testnets, I think we should try and do a stress test where we fill ~100 blocks on the network with transactions to see how clients (and potentially infrastructure) can handle this. In order to have people monitor things, it may make sense to schedule this in advance so the time is known.

@MariusVanDerWijden and @matkt have done such stress tests on Calaveras, so I assume the tooling could be re-used given sufficient ETH. I have >1M ETH on Ropsten + Goerli, which should suffice for a few rounds of 100 block tests across each network.

@matkt
Copy link

matkt commented Jun 18, 2021

yes it should be doable for me . I'm also setting up a Besu miner on ropsten to be able to test Besu as a miner

@timbeiko
Copy link
Collaborator Author

@matkt stress-tested Ropsten extensively and nothing broke 🎉 . Here are a few charts that show the baseFeePerGas over time:

basefee

baseFeePerGas over time on Ropsten since fork block. London sets the initial value at 1 gwei, large spikes up are the stress test, final spike down is when the spammer was shut down.

burn

ETH burnt per block during the stress test.

Will leave this issue open in case we decide to do a similar test either with several spammers in parallel, and/or on Goerli.

@timbeiko
Copy link
Collaborator Author

timbeiko commented Jul 9, 2021

Gave an update on ACD117, closing.

@timbeiko timbeiko closed this as completed Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants