From: Jonathan E. <jon...@si...> - 2005-04-27 19:08:04
|
Short answer: no, you don't care. :) The preferred way of running Spyce is as its own long-running process with -l; you can proxy this behind Apache if you want (letting Apache handle images and other static files), but even without that it's quite fast enough for almost any site. The reason this is a win is that as a single long-running process (fastcgi: not long-running; mod_python: multiple processes) you have a much easier time with caching data, running a connection pool, etc. If you really want FastCGI or mod_python (or your host limits you to that), I can't think of any reason to strongly prefer one over the other. mod_python is probably slightly faster but if you actually have a site so big that this is important, it will be worth your time to do some benchmarking of your own. -Jonathan John Reese wrote: > What are the pros and cons of using FastCGI vs. mod_python to invoke > spyce? mod_python (I think) runs in-process, whereas FastCGI runs a > second process which the Apache process forwards requests to via > TCP... is one faster or more reliable or secure than the other? |