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

bench: add constant rate mode to test failover #939

Open
costela opened this issue Dec 20, 2023 · 0 comments
Open

bench: add constant rate mode to test failover #939

costela opened this issue Dec 20, 2023 · 0 comments
Labels
proposal Enhancement idea or proposal

Comments

@costela
Copy link

costela commented Dec 20, 2023

Proposed change

Add a "constant rate" mode for the bench subcommand.

Use case

The current benchmark "as fast as it gets" mode is great, but it doesn't cover all cases one might want to inspect.

One such case is testing fail-over behavior of a nats setup. This could be better tested if we had - e.g. - a "constant rate" mode, that just constantly writes messages (for --pub) and counts them on the other side (for --pub).

This way one can fire messages at different rates and inspect either drop-rate or queue-fill-rate (depending on whether one is using nats streaming or not).

In our specific case we have leaves running on bare-metal and publishing (without streams) to a cluster on k8s. Cluster rollouts currently cause leaves to disconnect/reconnect and drop a few messages in between.

Contribution

I'd love to give it a try!

@costela costela added the proposal Enhancement idea or proposal label Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Enhancement idea or proposal
Projects
None yet
Development

No branches or pull requests

1 participant