Port the outdated pipeline patch against master #57
Conversation
|
Dynamic pipelined requests are handled correctly now. All known memory leaks related with pipelining were fixed. |
- Modification of 220df26 - script_request() has been renamed to script_request_single() - The new script_request() accepts the number of requests so that it generates a series of pipelined requests.
|
Thanks @trustin! I've actually been planning to deprecate the --pipeline option in favor of returning multiple concatenated requests from a script's request() function. This would allow for more realistic tests that request a number of different resources. I've finally gotten around to pushing a new pipeline branch, and example script (https://github.com/wg/wrk/blob/572274fe09be96a7af9fd701fe320ed4870a2ea3/scripts/pipeline.lua). |
|
My use case is to pipeline the same requests. Would it still be possible to do that without compromising throughput? |
|
Yes, if you precompute the requests in init() and just return the same global in request() throughput should be very high. I did some brief testing on my usual EC2 cc2.8xlarge instance with TSC clocksource and saw around 1.5M req/sec with pipeline.lua modified for a depth of 8. |
|
Thanks, @wg :-) |
This is a modification of 220df26 that works against master.