HHVM reported Siege bugs in >2.78 ?

[centminmod]

Hi curious if the bugs reported at http://hhvm.com/blog/9293/lockdown-results-and-hhvm-performance for Siege >2.78 been fixed in 3.1.0 yet ?

Siege — When benchmarking frameworks we used Siege 2.78, currently all versions of Siege 3 have known problems. In particular Siege 3.0.0 to 3.0.7 send incorrect HOST headers to ports other than 80, and 443, and Siege 3.0.8 and 3.0.9 occasionally send bad paths due to incorrect redirect handling.

[JoeDog]

I was not aware of that post so I'm not sure what they're talking about.
The port issue is fixed. I'm not sure what they're referring to when they
say it sends incorrect paths. I've entertained discussions about this with
others. I claim siege complies with the RFC.

Jeff

Hi curious if the bugs reported at
http://hhvm.com/blog/9293/lockdown-results-and-hhvm-performance for Siege

2.78 been fixed in 3.1.0 yet ?

Siege — When benchmarking frameworks we used Siege 2.78, currently all
versions of Siege 3 have known problems. In particular Siege 3.0.0 to 3.0.7
send incorrect HOST headers to ports other than 80, and 443, and Siege
3.0.8 and 3.0.9 occasionally send bad paths due to incorrect redirect
handling.

—
Reply to this email directly or view it on GitHub
#15.

[centminmod]

@JoeDog yeah i do not know what they mean about incorrect paths either so thought I'd ask :)

Just want to say love your work on Siege - been a long time fan and user http://wordpress7.centminmod.com/122/wordpress-super-cache-benchmark-siege-http-load-testing/ and love that you now have the code on Github :)

cheers

George

[JoeDog]

Thanks for the kind words, George. I appreciate it.

J.

On Fri, Jun 12, 2015 at 3:33 PM, George Liu (eva2000) <
[email protected]> wrote:

@JoeDog https://github.com/JoeDog yeah i do not know what they mean
about incorrect paths either so thought I'd ask :)

Just want to say love your work on Siege - been a long time fan and user
http://wordpress7.centminmod.com/122/wordpress-super-cache-benchmark-siege-http-load-testing/
and love that you now have the code on Github :)

cheers

George

—
Reply to this email directly or view it on GitHub
#15 (comment).

[JoeDog]

George,

I also like your entry on testing wp-supercache. Good stuff.

J.

On Fri, Jun 12, 2015 at 4:09 PM, Jeff Fulmer [email protected] wrote:

Thanks for the kind words, George. I appreciate it.

J.

On Fri, Jun 12, 2015 at 3:33 PM, George Liu (eva2000) <
[email protected]> wrote:

@JoeDog https://github.com/JoeDog yeah i do not know what they mean
about incorrect paths either so thought I'd ask :)

Just want to say love your work on Siege - been a long time fan and user
http://wordpress7.centminmod.com/122/wordpress-super-cache-benchmark-siege-http-load-testing/
and love that you now have the code on Github :)

cheers

George

—
Reply to this email directly or view it on GitHub
#15 (comment).

[centminmod]

thanks Jeff :)

[centminmod]

@JoeDog Jeff some more info on their encounted issues in Siege 3.x facebookarchive/oss-performance#48

[fredemmott]

I can't reproduce issues in 3.1.0; I'm keeping 3.x blacklisted in oss-performance for now until we have time to check that 3.1.0 gives similar results to 2.78 across the suite - average byte size of response, response code ratios, etc - this is a fairly time-consuming process, which we also go through whenever we benchmark a new version of PHP, HHVM, or some framework - not specific to Siege.

[fredemmott]

Filed facebookarchive/oss-performance#50 to investigate changing the blacklist from 3.* to 3.0.*