Hi, a few things:
By making the PHP benchmark computation intensive, you're really testing the efficiency of the php-cgi handler rather than cherokee. I agree it's important to test just for the sake of comparing all variables, but a better test might be to write a script to recursively call 2 or more pages or write a few pages that call each other n times and generate random content using PHP. This tests how fast PHP passes the page handling off to the interpreter and also how fast the interpreter passes the random content back to cherokee as well as testing the interpreter itself.
For a computation/memory intensive benchmark, a great one is generating prime numbers, storing each prime found in a growing array. If each prime number candidates are tested against each 'discovered' prime number in the array this becomes memory and CPU intensive at the same time. The benchmark can be the time it takes to calculate enough primes that the test system runs out of physical memory where lower = better. I've used a C program to test out kernel configurations and memory speed on systems before and it's pretty good. If you want it, I'll post it, but I'm not an accomplished PHP programmer.
Perhaps another good test here might be to show apache's performance with native PHP vs. PHP_CGI handling just as a basis for further comparison.
I'm quite interested in the benchmark results and will happily volunteer an AMD64 system for this testing if desired.
b) PHP:
- PHP info
- Computation-intensive PHP script (ideas welcomed)
- Memory-intensive PHP script (ideas welcomed)
_______________________________________________ Cherokee mailing list [email protected] http://www.0x50.org/cgi-bin/mailman/listinfo/cherokee
