Hi Eduardo, I didn't come back to you earlier since I wanted to be sure of my testings.
As previously said, I'm doing a fair and independent comparative benchmark of different web servers and web application servers, including Monkey. I also said that I won't use you test tool since it's obviously one of the slowest I've ever seen, and even when using it, it doesn't give the best results for Monkey. The main reason of the poor performance of it is that it doesn't use the multi-thread capabilities of “modern” multi-core CPUs (and I should stop to say modern since multi-core CPUs are available now for a full decade). Instead, I use both weighttp (from Lighttpd) as well as abc, that's nothing but an open source weighttp wrapper developed the G-WAN team and allowing to run weighttp several times within a loop that increases the number of simultaneous clients. Further, abc allows to save the benchmark results in CVS type files that you can then use to create graphics. So, let's go back to your “Baby”. I'm very frustrated when trying to benchmark Monkey and any simple PHP application such the trivial "Hello World!" since Monkey stops to respond as soon as there is very few connections. I guess it's a FASTCGI problem that you should take a look at it urgently (even using only weighttp) since due to the lack of response of Monkey, your product will be put out of the race in my paper, and with the explanation why it's discarded. Since I don't want to hurt nor your team or you when publishing the reason of such a failure to compete even with the good old dog Apache2, I would appreciate your view point on this very specific subject. Now, if you want to perform real, reliable, not biased and reproducible stress benchmarks of Monkey (as well as of any other web server), please use abc on your own test systems and then share with me what are your comparative results. They may differ from mine, but unfortunately I guess and bet not that much! Happy holiday season to both of your development team members, your friends and family and you. Cheers. Null4Ever. Note: To install abc, please do the following (this is valid on any Debian like distro as well as Ubuntu and its derivative such as LinuxMint) sudo apt-get -y build-dep libev sudo apt-get -y install libev-dev mkdir abc cd abc wget http://dist.chmorph.de/libev/libev-4.15.tar.gz tar -xzf libev-4.15.tar.gz ./configure make sudo make install wget http://as2.com/linux/tools/weighttp64.tar.bz2 tar -xjf weighttp64.tar.bz2 sudo cp weighttp64 /usr/local/bin/weighttp wget http://as2.com/linux/tools/abc.tar.bz2 tar -xjf abc.tar.bz2 gcc -02 abc.c -lpthread -o abc sudo cp abc /usr/local/bin Then you're done. Both weighttp and abc provide the command structure help when firing them without argument. e.g. to stress Monkey with the basic "hello world" written in php [<?php echo "Hello World!"; exit(200); ?>] using abc, start: abc monkey 127.0.0.1:80/hello.php I'm just curious of what result you'll get! Replace monkey with any other web server name such as apache2, Cherokee, etc. accordingly to the web server you wish to stress. If you need to use weighttp and abc on a 32 bit distro, replace weighttp64.tar.bz2 with weighttp32.tar.bz2 Hope this helps anyone willing to fairly stress any web server (successfully tested on Monkey, but also Apache2, Cherokee, Lighttpd and Nginx as well as of course G-WAN). _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
