search

tag1consulting / goose

Load testing framework, inspired by Locust
https://tag1.com/goose
Apache License 2.0
759 stars 69 forks source link

Machine-readable reports #504

Closed samoylovfp closed 2 years ago

samoylovfp commented 2 years ago

Solves https://github.com/tag1consulting/goose/issues/499 (once finished)

The idea is to have reports written into a json file, so further processing and merging can be made out of the process

samoylovfp commented 2 years ago

Didn't have time to get to it this week and I am on holiday next 3 weeks. I expect I'll return to this some time in the next 40 days

samoylovfp commented 2 years ago

We found out we can extract the need information from requests log.

mTsBucy1 commented 1 year ago

@samoylovfp May I ask how you further processed the data? Did you parse the json requests log via code? Or did you use a Spreadsheet application?

Because I am currently in the process of using the csv requests log (which lead to #515) and importing in Excel, where I can do more customized processing, and I was wondering what other paths there might be.

samoylovfp commented 1 year ago

We wrote our own small app using egui, that loads different benchmarking results and shows request time histograms on a log scale. The service that we benchmark has several caching layers and performance of these layers show up as several "humps" on the histograms, this helped us track changes to the overall performance as well as each cache layer