[ANN] wrecker - An HTTP Benchmarker

I am happy to announce the release of 'wrecker-0.1.3.2', a library for HTTP benchmarks. 'wrecker' makes it easy to benchmark complex API interactions, by providing a 'wreq' like interface for creating suites of HTTP benchmarks. For more detailed information, tutorials, and examples checkout the README.md https://github.com/skedgeme/wrecker/blob/master/README.md Additionally there is documentation on Hackage: https://hackage.haskell.org/package/wrecker. Cheers, Jonathan Fischoff

We're using Gatling at work http://gatling.io/docs/2.2.2/ (Scala
based), and I'm looking for similar tools in Haskell (if they don't
exist is a nice project to work on I find).
Do you have any idea why `wreck` produces inflated results?
On Wed, Oct 5, 2016 at 12:59 PM, Jonathan Fischoff
I am happy to announce the release of 'wrecker-0.1.3.2', a library for HTTP benchmarks.
'wrecker' makes it easy to benchmark complex API interactions, by providing a 'wreq' like interface for creating suites of HTTP benchmarks.
For more detailed information, tutorials, and examples checkout the README.md
https://github.com/skedgeme/wrecker/blob/master/README.md
Additionally there is documentation on Hackage: https://hackage.haskell.org/package/wrecker.
Cheers, Jonathan Fischoff
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

hvr's comment on reddit sums up the issues well:
https://www.reddit.com/r/haskell/comments/55ywoy/ann_wrecker_an_http_benchma...
`http-client` is not designed for this use case. It's header parsing is too
slow specifically.
`wrecker` and `wreck` are fine in the 10-100 range for typical requests (30
- 300 ms)
`wrecker` can and will get better (possibly with uhttpc under the hood),
but if you have to sequence API together with processing between to profile
your API, `wrecker` is a great option because there is nothing as accurate
(that I know of) that can do that well.
On Fri, Oct 7, 2016 at 6:56 AM, Damian Nadales
We're using Gatling at work http://gatling.io/docs/2.2.2/ (Scala based), and I'm looking for similar tools in Haskell (if they don't exist is a nice project to work on I find).
Do you have any idea why `wreck` produces inflated results?
I am happy to announce the release of 'wrecker-0.1.3.2', a library for HTTP benchmarks.
'wrecker' makes it easy to benchmark complex API interactions, by
On Wed, Oct 5, 2016 at 12:59 PM, Jonathan Fischoff
wrote: providing a 'wreq' like interface for creating suites of HTTP benchmarks.
For more detailed information, tutorials, and examples checkout the README.md
https://github.com/skedgeme/wrecker/blob/master/README.md
Additionally there is documentation on Hackage: https://hackage.haskell.org/package/wrecker.
Cheers, Jonathan Fischoff
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Good that the bottle neck is clearly identified. On a related topic, we're starting to benchmark our web services, and we're using http://gatling.io as benchmarking tool. It is Scala based and I'd like to write the benchmarking program in Haskell instead. However I need a tool that can record the duration of each requests, and maybe aggregate them and export this to some format (I don't care about the plots right now). I don't know of wrecker has this capabilities or maybe there are other tools that the Haskell community use for this purpose. Any hints? Op 7 okt. 2016 16:09 schreef "Jonathan Fischoff" < jonathangfischoff@gmail.com>:
hvr's comment on reddit sums up the issues well: https://www.reddit.com/ r/haskell/comments/55ywoy/ann_wrecker_an_http_benchmarking_library/d8f0svb
`http-client` is not designed for this use case. It's header parsing is too slow specifically.
`wrecker` and `wreck` are fine in the 10-100 range for typical requests (30 - 300 ms)
`wrecker` can and will get better (possibly with uhttpc under the hood), but if you have to sequence API together with processing between to profile your API, `wrecker` is a great option because there is nothing as accurate (that I know of) that can do that well.
On Fri, Oct 7, 2016 at 6:56 AM, Damian Nadales
wrote: We're using Gatling at work http://gatling.io/docs/2.2.2/ (Scala based), and I'm looking for similar tools in Haskell (if they don't exist is a nice project to work on I find).
Do you have any idea why `wreck` produces inflated results?
I am happy to announce the release of 'wrecker-0.1.3.2', a library for HTTP benchmarks.
'wrecker' makes it easy to benchmark complex API interactions, by
On Wed, Oct 5, 2016 at 12:59 PM, Jonathan Fischoff
wrote: providing a 'wreq' like interface for creating suites of HTTP benchmarks.
For more detailed information, tutorials, and examples checkout the README.md
https://github.com/skedgeme/wrecker/blob/master/README.md
Additionally there is documentation on Hackage: https://hackage.haskell.org/package/wrecker.
Cheers, Jonathan Fischoff
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
participants (2)
-
Damian Nadales
-
Jonathan Fischoff