Adding a command line option to specify a remote Siege client. #83
Conversation
Please note you must set up privileged SSH connection between the Server and Client. It is also necessary to modify IP tables to allow INPUT and OUTPUT between Server and Client. Remote Client is specified by --remote-siege=<user>@<host>, and is to be paried with --i-am-not-benchmarking.
|
Can someone please review? Thanks! |
|
@kevand900 This seems okay, but I don't know why it would be useful. |
|
Having the Siege client able to run on a separate machine better represents a real-world scenario, as well as freeing up cycles for HHVM to be fully exercised. |
|
Have you done any experiments showing that the results aren't extremely noisy? I have had concerns with a lot of the recent changes moving things off the box. Yes is it more realistic in that your requests will be coming from else where, but it also means you might be measuring bottlenecks other than the webserver performance, and degrade the reproducibility of results. |
|
@mofarrell We're aware of the potential pitfalls. The intention is to perform measurements on an isolated high-speed subnet. If you'd like, we can schedule a meeting to discuss what we have in mind. |
Please note you must set up privileged SSH connection between the Server and Client.
It is also necessary to modify IP tables to allow INPUT and OUTPUT between Server and Client.
Remote Client is specified by --remote-siege=user@host, and is to be paried with --i-am-not-benchmarking.