On Thursday 03 May 2001 13:01, Jason Byron wrote:
This may sound silly, but do you think it would be feasably to get some more speed out of Zope by combining it with TUX (the linux kernel based web server) ? Maybe build the python interpreter into it ?
TUX is a linux only thing ATM, so any integration of the two would have to be some sort of add on to a vanila zope.
TUX 2898.55 Requests per second AOLserver 603.14 Requests per second Apache 502.51 Requests per second Zope 60.57 Requests per second
There are important reasons why the figures are so different. In the case of TUX, the kernel server tries to do as little work as possible to translate a request into data flying out the NIC. Zope, on the other hand, at the very least checks to see if the requester has permisson to access that object, and often looks after other things like acquisition, setting caching headers and obviously executing content generating code. The easiest way for Zope to take advantage of TUX would be to have a TUX based caching reverse proxy sit in front of the Zope server. All of the images and other static content window dressing for the site which will always be served up to everybody can have cache TTLs set so they quickly end up in the proxy, which can serve them up as fast as they can go. If you still want to crank more speed out of zope, the next thing to do would be to profile the steps needed to serve up requests for static content where having a permission system matters, and look into optimizing that. John