k6

Yeah, we have this issue: https://github.com/loadimpact/k6/issues/140 But you can actually aggregate results already, if you use InfluxDB as results storage: you can have multiple k6 instances push results data to the same InfluxDB instance. Results are just time series samples, so there are basically no bad effects if you do this - you get all the results in a single db, with correct time stamps. The only difficulty lies in orchestrating the multiple k6 instances so they're in sync and you get the traffic levels you want (i.e. they ramp up/down at the same time). But for a simple ramp configuration, or a config where you run at a stable traffic level, it shouldn't be a problem.

If you're interested, here is the Github issue for Websockets support in k6: https://github.com/loadimpact/k6/issues/178 We'd really appreciate any comments/feedback you may have on exactly how it should be implemented.

Thanks for the nice words! If you see anything missing, don't hesitate to create an issue about it on Github (https://github.com/loadimpact/k6). We're trying really hard to build the things people ask for. About CSV output though, we have JSON output with single request timings, see https://docs.k6.io/docs/results-output#section-json-output Is JSON useful to you, or do you prefer CSV?