-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support multiple workers for rate
bench mode
#170
Comments
AnnaShaleva
added
U2
Seriously planned
S2
Regular significance
I2
Regular impact
feature
Completely new functionality
labels
May 13, 2024
AliceInHunterland
added a commit
that referenced
this issue
May 14, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 14, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 15, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 15, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 16, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 16, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 16, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 16, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 16, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 16, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 21, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
AliceInHunterland
added a commit
that referenced
this issue
May 22, 2024
We need to run multiple workers for the rate mode and share the load between them. Close #170 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently
rate
bench mode produces single-threaded network load:neo-bench/cmd/bench/main.go
Lines 52 to 53 in 7ee7f71
It's not enough for real networks (ref. #160), we're facing with the issue when loader can't produce the necessary load level.
Describe the solution you'd like
We need to run multiple workers for the
rate
mode and share the load between them. The number of workers may be hard-coded for the first time. A tricky part is to properly synchronize these workers to produce the desired RPS, this should be handled with care.The text was updated successfully, but these errors were encountered: