Hacker News Reader

Comment by jtmoulia | Hacker News Reader

I'd love to use this to test my application, but after reading through the docs, I'm not quite sure how to get the setup I'd like:

My application is a server which clients login and then issue commands to. As I'm imagining it, a user load generator would be creating and logging in users. But this is where I get fuzzy... should the user task also create a load generator which issues commands against the application as that user? Seems pretty simple, hopefully it's possible !

Excited to try this out.

View on HN

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 trigger happens asynchronously so there is no way to thread state between triggers.

If there is enough interest I'd be happy to extend it to handle synchronous load generators where threading state makes sense. With that use case though, it'd be impossible to guarantee that the actual load matches the load_spec in all circumstances.

If you wish to keep state between triggers you have to implement this outside of ponos at this stage.

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.

In that case, would the caller be responsible for ramping up the number of users?

I am also interested in load testing stateful sessions e.g. log in, wait, do stuff, wait, log out. Using ponos this could be done by spawning a (gen_server-) process in the task which runs the session and then terminates. In this scenario the load function would model the arrival rate of the users.

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 call_counter reaches a threshold.

Replying to my own post here, this is an example: https://gist.github.com/odo/6c59f604fda6390d034a

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.

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.

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

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.

Reply on news.ycombinator.com