You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Command line arguments / config
List all command line arguments or config properties ghz --insecure \ --call apigateway.Service/Process \ -D ./data.json \ --rps 1000 --duration=10m \ --connect-timeout=1s \ --lb-strategy=round_robin \ --cpus=16 \ --concurrency=16 \ --async \ dns:///any.net:82
Describe the bug
A clear and concise description of what the bug is.
After running the test, new fruits of the application appear. but the load is not distributed on them, although I add "--lb-strategy=round_robin" to the arguments
To Reproduce
Steps to reproduce the behavior:
launch ghz
wait for the application to scale
the graphs show that the load goes only to the old pods, and does not go to the new ones.
Expected behavior
A clear and concise description of what you expected to happen.
the ability to fine-tune balancing
Environment
ubuntu
ghz: 0.117.0
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Command line arguments / config
List all command line arguments or config properties
ghz --insecure \ --call apigateway.Service/Process \ -D ./data.json \ --rps 1000 --duration=10m \ --connect-timeout=1s \ --lb-strategy=round_robin \ --cpus=16 \ --concurrency=16 \ --async \ dns:///any.net:82
Describe the bug
A clear and concise description of what the bug is.
After running the test, new fruits of the application appear. but the load is not distributed on them, although I add "--lb-strategy=round_robin" to the arguments
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
the ability to fine-tune balancing
Environment
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: