Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can anyone explain more about vegeta report? #293

Closed
contactparthshah opened this issue Jun 13, 2018 · 6 comments
Closed

Can anyone explain more about vegeta report? #293

contactparthshah opened this issue Jun 13, 2018 · 6 comments

Comments

@contactparthshah
Copy link

contactparthshah commented Jun 13, 2018

Question

I ran test using vegeta and it has generated following report:

Requests      [total, rate]            200, 19.35
Duration      [total, attack, wait]    11.978051256s, 10.337022623s, 1.641028633s
Latencies     [mean, 50, 95, 99, max]  646.318364ms, 451.048775ms, 1.697808872s, 2.128540278s, 2.641028633s
Bytes In      [total, mean]            84733, 423.67
Bytes Out     [total, mean]            0, 0.00
Success       [ratio]                  93.50%
Status Codes  [code:count]             403:13  200:187
Error Set:
403 Forbidden

It will be good if anyone can help me to understand the report.

what to deduce from Duration [total, attack, wait] 11.978051256s, 10.337022623s, 1.641028633s ?

What to deduce from Latencies [mean, 50, 95, 99, max] 646.318364ms, 451.048775ms, 1.697808872s, 2.128540278s, 2.641028633s ?

what to deduce from Bytes Out [total, mean] 0, 0.00 ?

why Bytes Out is 0 ?

@tsenart
Copy link
Owner

tsenart commented Jun 15, 2018

what to deduce from Duration [total, attack, wait] 11.978051256s, 10.337022623s, 1.641028633s ?

  • attack is the amount of time taken issuing all requests (total - wait)
  • wait is the amount of time waiting for the response to the last request (total - attack)
  • total is the total amount of time taken in the attack (attack + wait).

What to deduce from Latencies [mean, 50, 95, 99, max] 646.318364ms, 451.048775ms, 1.697808872s, 2.128540278s, 2.641028633s ?

  • latency is the amount of time taken for a response to a request to be read (including the body).
  • mean is the arithmetic mean / average of the latencies of all requests in an attack.
  • 50, 95, 99 are the 50th, 95th an 99th percentiles, respectively, of the latencies of all requests in an attack. To understand more about why these are useful, I recommend this article from @tylertreat.
  • max is the maximum latency of all requests in an attack.

what to deduce from Bytes Out [total, mean] 0, 0.00 ?
why Bytes Out is 0 ?

The BytesOut section describes summary metrics of the number of bytes sent out in request bodies during attacks. If you haven't defined a body, it will be zero.

@tsenart
Copy link
Owner

tsenart commented Jun 15, 2018

Please re-open if you have further questions.

@tsenart tsenart closed this as completed Jun 15, 2018
@contactparthshah
Copy link
Author

Thank you.

@jzaefferer
Copy link

Those details would be pretty useful in the readme! I'm still not quite sure what to make of this, after running with -duration=5s:

Duration [total, attack, wait] 26.126396344s, 4.982672s, 21.143724344s

@tsenart
Copy link
Owner

tsenart commented Dec 18, 2018

Hi @jzaefferer! Is the explanation in the comment above clear to you?

@jzaefferer
Copy link

Yeah, I think its fine. I didn't expect duration (of the test) to be limited to issuing requests, not for them to also be answered.

So yes, getting the info above into the readme, so others don't have to dig around closed issues for it, would be nice

tsenart pushed a commit that referenced this issue Dec 19, 2018
tsenart pushed a commit that referenced this issue Dec 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants