I did some benchmarks of aolserver vs lighthttpd on plain files of
various sizes, on my 8cpu 64 bit server.
For 3 runs, with a 4k text file, the lighthttpd stats were 15103.87/
s, 14845.20/s and 15307.17/s, vs (as Dossy reports http://dossy.org/
archives/000517.html) aolserver's 15237.00/s.
On 2007.09.25, John Buckman [EMAIL PROTECTED] wrote:
I did some benchmarks of aolserver vs lighthttpd on plain files of
various sizes, on my 8cpu 64 bit server.
Thanks! This is all fantastic information to have!
www64:/b# ab -c 5 -n 5 http://images.bookmooch.com/x.txt
Since your
www64:/b# ab -c 5 -n 5 http://images.bookmooch.com/x.txt
Since your machine is a 2-CPU 8-core box, could you try runs with -c 8
and -c 16? It may have no effect, but it'd be nice to know that for
sure.
I get more-or-less the same numbers at -c 8, -c 16 and -c 32, varying
about 100
Jeff,
I developed a templating system which is safe for untrusted users.
Actually that was one of the main goals. The sources, somewhat messy are at:
http://rmadilo.com/m2/servers/rmadilo/modules/tcl/twt/packages/view/
The templates are 'compiled' into a Tcl script.
The template compiler is a
I'm trying to configure AOLserver 4.5 for a custom 404 page, and my Config from
previous versions is:
ns_section ns/server/$service_name/redirects
ns_param 404 /file-not-found
but I just get the default 404 page. Any ideas why? I used the 4.5 RPM from
Project Open.
Titi Ala'ilima
Lead
Didn't find this searching online but I finally found in my own email archives
that there was a bug patched last year, which must have preceded this RPM.
Titi Ala'ilima
Lead Architect
MedTouch LLC
1100 Massachusetts Avenue
Cambridge, MA 02138
617.621.8670 x309
From: AOLserver Discussion
Hi Titi,
Verify that your file paths are ok. There's an example in Panoptic's
wiki:
http://panoptic.com/wiki/aolserver/AOLserver_Cookbook#Customizing_error_pages
Good luck,
Juan José
El Tue, 25 Sep 2007 11:15:11 -0700 , Titi Alailima [EMAIL PROTECTED]
escribió:
I'm trying to configure
This is an ACS-based system, which abstracts URLs so you don't need the
extension. Just to be sure though I tried it with a full file name and it
still didn't work. However, I believe this is the error John Buckman and Derek
Keller found around July of last year and Jim Davidson fixed. I