Skip to content

Releases: tsenart/vegeta

Revert recent timeout behaviour change

23 May 21:55
Compare
Choose a tag to compare

A recent change had an unintended effect of considering time to read response bodies in each request deadline. This has been reverted.

Allow case sensitive headers in attacks

23 May 20:49
Compare
Choose a tag to compare

This release enables using case sensitive headers in attacks. Thanks to @hi-t-ch for the initial discussion and to @GeertJohan to follow up.

Major performance improvements

16 Apr 16:46
Compare
Choose a tag to compare

This release brings major improvements to vegeta's performance and how much throughput it can generate reliably.

  • Major performance improvements that allow much higher attack rates
  • Expose connections flag in the attack command
  • Add global cpu and heap profiling flags
  • Measure actual attack rate and print it in relevant reporters

Thanks to @vdel26 who kicked this off with #120 and to @giltene for inspiration with his previous feedback and work on https://github.com/giltene/wrk2.

Plot reporter improvements

02 Apr 16:33
Compare
Choose a tag to compare
  • Update dygraph to latest version
  • Improve plot reporter screenshot rendering by using html2canvas.js
  • Improve plot reporter performance

Thanks to @nathany for reporting: #119

Allow spaces in report histogram flag format

23 Mar 19:14
Compare
Choose a tag to compare

This release allows spaces in the report command hist reporter flag format. This means that passing hist[0,5ms] and hist[0, 5ms] to the -reporter flag of the report command is equivalent.

Version flag, default dumper and regression fix

12 Mar 11:49
Compare
Choose a tag to compare

This release adds a --version flag to the vegeta command, sets the default dumper as json so you don't have to type the extra flag for the common use case and fixes a regression introduced by the previous release.

Bug fix

11 Mar 14:54
Compare
Choose a tag to compare

This release fixes a bug that incorrectly counted the number of bytes received in response bodies.
Thanks to @pwaller for reporting it in #113.

Only use status text as error message

03 Jan 17:31
Compare
Choose a tag to compare

This release fixes a bug introduced in the previous release which included full response bodies as error messages.
#108

Treat [200...399] status code range as errors

02 Jan 14:11
Compare
Choose a tag to compare

This release fixes a bug that didn't treat responses with status codes outside the [200...399] range as errors. Thanks to @davideicardi for reporting it.

Dump command

21 Nov 11:51
Compare
Choose a tag to compare

This release implements a dump command which outputs piped attack results in different formats.

$ vegeta dump -h
Usage of vegeta dump:
  -dumper="": Dumper [json, csv]
  -inputs="stdin": Input files (comma separated)
  -output="stdout": Output file

-inputs

Specifies the input files containing attack results to be dumped. You can specify more than one (comma separated).

-output

Specifies the output file to which the dump will be written to.

-dumper

Specifies the dump format.

json

Dumps attack results as JSON objects.

csv

Dumps attack results as CSV records with six columns.
The columns are: unix timestamp in ns since epoch, http status code,
request latency in ns, bytes out, bytes in, and lastly the error.