On 09/05/2010, at 22:24, Miguel Angel wrote: > Here it's the benchmarking tool I worked on a "few" months ago. > > http://code.google.com/p/easybench/ > > It could be used to track perfomance changes between differents versions of > cherokee, which could be quite useful (it would need something like measuring > cpu ticks in a virtual machine, as Stephan sugested). > > As can be readen in the project page, it's made of two part, the server, and > the client (I tested it on standalone machines, and most of my problems came > from operating system limits on the client machine -wow-). > > These are the settings for building/running/testing different servers from > sources: > http://code.google.com/p/easybench/source/browse/trunk/server-deployment/settings.py > > And those are the settings for the tested servers: > http://code.google.com/p/easybench/source/browse/#svn/trunk/server-deployment/conf_templates/cherokee-0.99.20%3Fstate%3Dclosed > > It was prepared to get information about requests, failed requests and memory > usage on server, but I think the last version (dumping the final results) was > lost from my laptop disk crash... , I'll try to check the backups.
Thanks a million of the effort, and for letting us know about it on the Cherokee Summit. I'd love to figure how we could integrate this in some sort of building system so Cherokee could be automatically tested for each new release. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
