Hi Guys, It's been a while since I last looked at Cherokee, so I thought I might show some performance findings, along with the same tests applied to our current web server, as well as a few feature wishes.
First of all, we're currently using Zeus as our web server. It's very fast, easy to configure and maintain, has minimal downtime, and is generally very reliable. The big problem is its price tag. Here are the important values for Cherokee/0.4.24: ab -n 10000 -c 10 http://localhost/test.dat Time per request: 10.197 [ms] (mean) Time per request: 1.020 [ms] (mean, across all concurrent) Requests per second: 980.64 [#/sec] (mean) Transfer rate: 42241.11 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 2 3 4.2 3 72 Processing: 3 5 5.0 5 74 Waiting: 0 2 4.6 2 72 Total: 8 9 6.3 9 76 ab -n 10000 -c 10 -k http://localhost/test.dat Requests per second: 1588.38 [#/sec] (mean) Time per request: 6.296 [ms] (mean) Time per request: 0.630 [ms] (mean, across all concurrent) Connection Times (ms) min mean[+/-sd] median max Connect: 0 0 0.1 0 5 Processing: 3 5 5.2 5 72 Waiting: 0 2 3.5 2 69 Total: 3 5 5.2 5 72 And for Zeus/4.3: ab -n 10000 -c 10 http://localhost/test.dat Requests per second: 1572.63 [#/sec] (mean) Time per request: 6.359 [ms] (mean) Time per request: 0.636 [ms] (mean, across all concurrent) Connection Times (ms) min mean[+/-sd] median max Connect: 0 1 3.2 2 64 Processing: 2 3 4.5 4 65 Waiting: 0 1 3.0 1 64 Total: 4 5 5.3 5 66 ab -n 10000 -c 10 -k http://localhost/test.dat Requests per second: 2269.38 [#/sec] (mean) Time per request: 4.406 [ms] (mean) Time per request: 0.441 [ms] (mean, across all concurrent) Connection Times (ms) min mean[+/-sd] median max Connect: 0 0 0.1 0 4 Processing: 3 3 5.1 3 65 Waiting: 0 1 4.1 1 64 Total: 3 3 5.1 3 65 Also, there are features that we require before we could consider using Cherokee. While I know some of them are planned, and some even started, what is the status of each of these? (Some of these might already be implemented, and I've just missed them.) 1. FastCGI content generators and authorisers. An absolute must. 2. FastCGI management (so idle FastCGIs are shut down). 3. Loading of virtual server configurations from an SQL database (or another source) and only starting them when they're needed. 4. Request Rewriting, either in Apache's or Zeus's flavours. 5. An easy-to-use web UI for configuring a cluster of servers, rather than just one. Otherwise, great work. We're already using Cherokee for one service that doesn't have quite such high requirements. -- Rob Kendrick, Pepperfish Ltd. +44 (0)845 226 4146 www.pepperfish.net PGP signed or encrypted mail welcome Key ID: 3651D17A _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
