Skip to content

Update Spamoor to new configuration #2480

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.

Sign up for GitHub

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

Jump to bottom
Open
mpaulucci opened this issue Apr 15, 2025 · 3 comments · May be fixed by #2627
Open

Update Spamoor to new configuration #2480

mpaulucci opened this issue Apr 15, 2025 · 3 comments · May be fixed by #2627
Assignees
@fedacking
Labels
ci Github actions, build, tests, etc L1 Ethereum client

Comments

@mpaulucci
Copy link
Collaborator

See this message: https://discord.com/channels/595666850260713488/892088344438255616/1361762938427277415

Heads up: spamoor config update in the kurtosis ethereum package

We've revamped how spamoor is configured and removed the spamoor_blobs service completely.

Instead, spamoor now takes a list of spammers to run:

additional_services:
  - spamoor
spamoor_params:
  spammers:
    - scenario: eoatx
      config:
        throughput: 200
    - scenario: blobs
      config:
        throughput: 6

When not specifying any spammer, there are 2 default spammers (eoatx & blobs-combined) launched.

The new spamoor service comes with a web UI/API to manage spammers (start/stop/update) on the fly as needed.

If you're using the old config, you'll need to update.
The following top-level params have been removed in favor for the new spammers list: scenario, throughput, max_pending, max_wallets.

Let us know if you run into issues!
@mpaulucci mpaulucci added ci Github actions, build, tests, etc L1 Ethereum client labels Apr 15, 2025
@fedacking fedacking self-assigned this Apr 24, 2025
@mpaulucci mpaulucci mentioned this issue Apr 24, 2025
Closed
@mpaulucci
Copy link
Collaborator Author

Add to this network_params_tx.yaml so that it runs on the CI, see: #1456

@fedacking
Copy link
Contributor

Adding a small question, which discord server is the message from?

@fedacking
Copy link
Contributor

Those configuration changes haven't been downstreamed to lambdaclass/ethereum-package. Should I set it up with the previous config with a note when we update or try to update our fork of the ethereum-package?

@fedacking fedacking linked a pull request Apr 28, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fedacking fedacking

Labels
ci Github actions, build, tests, etc L1 Ethereum client
Projects
ethrex_l1
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci(l1): Updated CI to include spamoor and new version of ethereum-package lambdaclass/ethrex
2 participants
@mpaulucci @fedacking