*Finally* ran this through my test cases with three poundings with wrk. Here are the requests/sec:
httpd (2.4 + proposed UDS patch) Req/Sec 147.34 28.89 282.00 71.38% Req/Sec 147.48 27.18 250.00 67.75% Req/Sec 147.87 28.17 239.00 70.94% nginx Req/Sec 180.99 27.81 311.00 77.92% Req/Sec 183.46 32.59 369.00 72.44% Req/Sec 176.81 28.18 325.00 71.99% Three samples with 30 second tests is far from scientific, but I think illustrates general timings (and, more importantly, that it works!). -- Daniel Ruggeri On 11/14/2013 9:56 AM, Jim Jagielski wrote: > What the heck. STATUS is updated w/ the backport proposal > and the patch... > > On Nov 14, 2013, at 7:46 AM, Jim Jagielski <j...@jagunet.com> wrote: > >> I'd like to yes, but I don't want to push 2.4.7 out much >> longer. There are other things in STATUS, like the event patches >> which have been running on ASF infra for quite awhile, that >> I'd like to see in 2.4.7 when we ship. We can save UDS for >> 2.4.8 and make that a(nother) reason for people to upgrade. >> >> On Nov 13, 2013, at 8:27 PM, Daniel Ruggeri <drugg...@primary.net> wrote: >> >>> On 11/13/2013 10:39 AM, Jim Jagielski wrote: >>>> Now that APR 1.5 is soon-to-be released, we are good for >>>> a release of 2.4.7. >>>> >>>> I propose a T&R next week (I'll RM) and would request >>>> that people look thru STATUS for some remaining backports. >>> Are you hoping to push for UDS in 2.4.7? Seems like a great feature... >>> >>> (yes, I'm guilty in not testing out the latest trunk patches and >>> providing feedback - I had planned to do that last week... and this >>> week... and probably next week) >>> >>> -- >>> Daniel Ruggeri >>>
