Show HN: K6 – developer-centric load testing using Go and JavaScript
1–10 of 26 posts
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#2k6 is our attempt at creating a modern, developer/devops-centric load testing tool suitable for automation. It is released as open source on Github, scriptable in JavaScript (ES6), and built on a Golang core that provides good speed and concurrency/scalability.
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#3Does this support websocket?
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#4This looks incredible for work I was previously using Tsung / Gatling for.
One request: please allow the output of either a) a CSV log of every request and it's timing or b) a configurable histogram of request timing, not just some percentiles and averages. That info is pretty much required for doing any more advanced analysis beyond "the service is fast enough". https://github.com/tsenart/vegeta does this really well (but doesn't have the scripting abilities of this tool).
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#5This looks incredible for work I was previously using Tsung / Gatling for. One request: please allow the output of either a) a CSV log of every request and it's timing or b) a configurable histogram of request timing, not just some percentiles and averages. That info is pretty much required for doing any more advanced analysis beyond "the service is fast enough". https://github.com/tsenart/vegeta does this really wel…
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?
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#6Does this support websocket?
No, there is currently no support for websockets. We have been asked for this a couple of times though, and are considering bumping up the priority for a websockets implementation.
As of now, k6 can do standard http, https (and it also supports HTTP/2)
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#7Does this support websocket?
No, there is currently no support for websockets. We have been asked for this a couple of times though, and are considering bumping up the priority for a websockets implementation. As of now, k6 can do standard http, https (and it also supports HTTP/2)
Thanks for the info! Would love ws suppprt!
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#8Does this support websocket?
No, there is currently no support for websockets. We have been asked for this a couple of times though, and are considering bumping up the priority for a websockets implementation. As of now, k6 can do standard http, https (and it also supports HTTP/2)
Yes, websockets please! Great! Thank you!
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#9This looks incredible for work I was previously using Tsung / Gatling for. One request: please allow the output of either a) a CSV log of every request and it's timing or b) a configurable histogram of request timing, not just some percentiles and averages. That info is pretty much required for doing any more advanced analysis beyond "the service is fast enough". https://github.com/tsenart/vegeta does this really wel…
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?
That looks like what I'm looking for, thanks! Is there documentation of the format of those JSON logs? CSV would probably be a useful addition just for ease of ingestion into analysis tools and databases.
Once I get a chance to test this out, I'll definitely report any issues through GH.
Re: Show HN: K6 – developer-centric load testing using Go and JavaScript
#10At work, we had to do some load testing and we used Vegeta: https://github.com/tsenart/vegeta
Had anyone used both to point out the main differences from k6?