Skip to content

Conversation

ganeshvanahalli
Copy link
Collaborator

@ganeshvanahalli ganeshvanahalli commented Oct 1, 2025

This PR syncs the master and release branches of nitro-testnode

@cla-bot cla-bot bot added the s label Oct 1, 2025
if $l3_traffic; then
echo == create l3 traffic
run_script send-l3 --ethamount 10 --to user_traffic_generator --wait
run_script send-l3 --ethamount 0.0001 --from user_traffic_generator --to user_traffic_generator --wait --delay 5000 --times 1000000 > /dev/null &
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

out of curiosity - why do we need --delay?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think its duration between successive transactions-

if (argv.delay > 0) {

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I apologize for the poor wording of the question. Why do we need to set any delay? It looks like we have to do 1M transactions and sleep for 5s after every one

I see that this has already been the case, so of course I'm not treating this as a blocker or anything; it's just my curiosity... 🙈

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we set the delay between tx to move the chain in regular interval so that the chain keeps progressing- like new tx keep coming in causing the batch poster to post batches regularly, assertions being posted too etc etc... Without the delay 1M txs would be completed pretty quickly beating the purpose of traffic.. does that make sense?

@ganeshvanahalli
Copy link
Collaborator Author

closed by #155

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants