[jtmoulia]

Thanks for the explanation!

Not the most flexible solution, but if you want the load spec to be authoritative you could allow it to recursively specify a different load generator rather than a task_runner. Instead of running a task, it would start a new load generator.

... hope I got some of the terminology right.

[jool]

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 load generator per user. Let me know if you have any questions.

[jtmoulia]

Thank you for this! I'll be trying it out in about a month, and I'll let you know hos it goes.

[jool]

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 indexed by name.

You would then log in the user during the init state.

I'm on the subway but I'll describe it more in detail when I get home.