Raised by @alter123 in #26, split out so it does not get lost under the autoscaler question.
Two related things:
A client cannot be autoscaled. client declares no scaleField, so an autoscaler wired to one has nothing to resize and does nothing. Since #26 that at least says so in the panel rather than sitting silent, but it is worth asking whether it should be possible at all. A load generator is not really a fleet you scale to meet demand, it IS the demand, so the honest answer may be that this is a modelling boundary rather than a gap.
There is no way to say how the rate should change over time. This one is a real gap and it is already half built. Ramp, spike and diurnal patterns are implemented in the engine and tested, and there is no control in the inspector to reach them, so every design runs at whatever the slider is pinned to. That is tracked in TODO.md and is the piece most likely to answer what was actually being asked for here.
Raised by @alter123 in #26, split out so it does not get lost under the autoscaler question.
Two related things:
A client cannot be autoscaled.
clientdeclares noscaleField, so an autoscaler wired to one has nothing to resize and does nothing. Since #26 that at least says so in the panel rather than sitting silent, but it is worth asking whether it should be possible at all. A load generator is not really a fleet you scale to meet demand, it IS the demand, so the honest answer may be that this is a modelling boundary rather than a gap.There is no way to say how the rate should change over time. This one is a real gap and it is already half built. Ramp, spike and diurnal patterns are implemented in the engine and tested, and there is no control in the inspector to reach them, so every design runs at whatever the slider is pinned to. That is tracked in TODO.md and is the piece most likely to answer what was actually being asked for here.