Graham Dumpleton
grahamd at dscpl.com.au
Sun May 1 04:07:58 EDT 2005
On 01/05/2005, at 4:29 PM, vegetax wrote: > Basically is a version of publisher handler,targeted to a specific > webframework,the publisher handler is sloww cause it tries to be > everything,too generic, my handler will just serve .py scripts and > thats > all, is not meant to serve several resources,or work with user_dir or > have > subdirectories, since subdirectories will be mapped to python packages > by > the handler. > I am obsessed about making it fast, so thats why i wanted to get that > info > in one step instead of two. Do you actually have any hard data to support your claim that publisher is too slow? Most web applications are slow because of stuff like database access, need to support sessions and session databases, choice of mechanism to generate HTML etc. Ie., the delays aren't in the switching mechanism but what the handlers actually do. Making trivial changes to make something run as one step isn't necessarily going to help. Overall network lag is probably still going to swamp any improvement you may get. If the issue is that the server is too loaded, then you need to look how Apache is configured, whether an alternate MPM would be better and whether you should employ load balancing techniques. Sorry, but I am always very skeptical when the first thing people say is that something has to run as fast as possible or that something is just too slow. ;-) Graham
|