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
To appropriately test the systems under load, we have controllers with 45+ machines backing behind them.
It is very common to run an NBomber test with 45 agents to fail because NBomber is unable to connect all to all of them. The test doesn't often begin and developers are faced with an NotAllAgentsAvailable exception.
To reproduce this, we can create a basic NBomber test application with one scenario that does nothing. Spawn many agent processes on multiple machines. We will encounter this problem about 50% of the time with 45 agents and 100% of the time with 135 agents (3 agents per machine).
This makes scaling our tests to the target load nearly impossible.
The text was updated successfully, but these errors were encountered:
To appropriately test the systems under load, we have controllers with 45+ machines backing behind them.
It is very common to run an NBomber test with 45 agents to fail because NBomber is unable to connect all to all of them. The test doesn't often begin and developers are faced with an NotAllAgentsAvailable exception.
To reproduce this, we can create a basic NBomber test application with one scenario that does nothing. Spawn many agent processes on multiple machines. We will encounter this problem about 50% of the time with 45 agents and 100% of the time with 135 agents (3 agents per machine).
This makes scaling our tests to the target load nearly impossible.
The text was updated successfully, but these errors were encountered: