Sure thing. I guess you could even spawn a task that generates new load_generators. In that scenario I guess it could be useful to have the possibility to configure a load generator that terminates after the…
I've put together a really trivial example here (in semi-pseudo code): https://gist.github.com/jool/1e83b22fec9d948194a4. In the example I've modeled each of your uses as a load generator. So you would have to add one…
So. What you could do is implement your own task_runner. For instance, if you wish to represent each user as a load generator, your task_runner's state could store each load generator's user information in the state…
For your particular use case though I'd just login and pass the user information as part of the task. The load_generator would then not be concerned about logging in but only issuing commands.
Where ponos is at currently its main purpose in the world is specialise in generating simple or complex load patterns. A load_generator in essence is just a process generating triggers at requested frequency. Every…
Something the author (me) is aware of. See the Notes section of the README (https://github.com/klarna/ponos#ref1). The original name is based on the Greek god of hard labor and toil (http://en.wikipedia.org/wiki/Ponos).
Sure thing. I guess you could even spawn a task that generates new load_generators. In that scenario I guess it could be useful to have the possibility to configure a load generator that terminates after the…
I've put together a really trivial example here (in semi-pseudo code): https://gist.github.com/jool/1e83b22fec9d948194a4. In the example I've modeled each of your uses as a load generator. So you would have to add one…
So. What you could do is implement your own task_runner. For instance, if you wish to represent each user as a load generator, your task_runner's state could store each load generator's user information in the state…
For your particular use case though I'd just login and pass the user information as part of the task. The load_generator would then not be concerned about logging in but only issuing commands.
Where ponos is at currently its main purpose in the world is specialise in generating simple or complex load patterns. A load_generator in essence is just a process generating triggers at requested frequency. Every…
Something the author (me) is aware of. See the Notes section of the README (https://github.com/klarna/ponos#ref1). The original name is based on the Greek god of hard labor and toil (http://en.wikipedia.org/wiki/Ponos).