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
Load generator does some state setup in scheduleLoadGeneration. Without the setup, we can't generate load correctly (for example, we can't generate load if we don't populate available accounts to choose from). However, it looks like core triggers load generation via generateLoad rather than scheduleLoadGeneration. Most of the time the first call to generateLoad is a no-op, since we compute the amount of load to generate based on elapsed time, but occasionally if the function takes a bit longer, we try to generate load and fail due to inadequate setup. We should refactor the startup code such that we perform all the necessary setup in the first call to generateLoad (and not in scheduleLoadGeneration, as it should only be in charge of rescheduling the callback)
The text was updated successfully, but these errors were encountered:
Load generator does some state setup in
scheduleLoadGeneration
. Without the setup, we can't generate load correctly (for example, we can't generate load if we don't populate available accounts to choose from). However, it looks like core triggers load generation viagenerateLoad
rather thanscheduleLoadGeneration
. Most of the time the first call togenerateLoad
is a no-op, since we compute the amount of load to generate based on elapsed time, but occasionally if the function takes a bit longer, we try to generate load and fail due to inadequate setup. We should refactor the startup code such that we perform all the necessary setup in the first call togenerateLoad
(and not inscheduleLoadGeneration
, as it should only be in charge of rescheduling the callback)The text was updated successfully, but these errors were encountered: