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

Output is garbled #45

Closed
spadgos opened this issue Feb 28, 2014 · 8 comments
Closed

Output is garbled #45

spadgos opened this issue Feb 28, 2014 · 8 comments

Comments

@spadgos
Copy link

spadgos commented Feb 28, 2014

selection_008

@spadgos
Copy link
Author

spadgos commented Feb 28, 2014

Don't worry... just RTFM'd.

$ vegeta attack ... | vegeta report

@spadgos spadgos closed this as completed Feb 28, 2014
@tsenart
Copy link
Owner

tsenart commented Feb 28, 2014

🍊

@tsenart
Copy link
Owner

tsenart commented Feb 28, 2014

@spadgos: You got me curious in regards to what you're load testing...

@spadgos
Copy link
Author

spadgos commented Feb 28, 2014

spotify.com

@tsenart
Copy link
Owner

tsenart commented Feb 28, 2014

Thought so.

@tsenart
Copy link
Owner

tsenart commented Feb 28, 2014

With a single target, it's idiomatic to do it like this:

$ echo "GET http://spotify.com" | vegeta attack -rate=100 -duration=3s | tee results.dat | vegeta report

That tee will save the results to results.dat while piping them through too. So you can afterwards run different reports on the same data.

$ cat results.dat | vegeta report -reporter=plot > results.html

@spadgos
Copy link
Author

spadgos commented Feb 28, 2014

Could be useful to add this to vegeta -h

@tsenart
Copy link
Owner

tsenart commented Feb 28, 2014

Yeah, I think you're right. I'll improve the the output of vegeta -h

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

2 participants