Reply to thread

Message: [QUOTE="Austin Ziegler, post: 4464573"] This is incorrect. Python scripts that aren't run as .pyc files will have to be recompiled every time. PHP/Zend has to be configured correctly. Using Ruby as a CGI does require that the files be compiled on every read, but this is the same of any .py or .pl or non-Zend .php file. Rails works best as if it were an application server using FastCGI as a backend. With mod_proxy, it is certainly possible to use the Webrick server as an application server via Apache. Ruby executes plenty fast, and the script compile step is fast, too. Consider -- the *whole* of the very high level framework *and application* represented by Rails compiles in under a second. This would be like compiling Struts and all sorts of other helper items from scratch on every call. The performance you were epxeriencing has nothing to do with Ruby and everything to do with the depth of the framework that Rails provides. Wrong. Pure CGI for *Rails* is useless, but not for many other things. FastCGI is better than mod_ruby, as far as I can tell. Additionally, it is my understanding that lighttpd and FastCGI are even better than Apache, which is a bit of a resource hog. (I'm looking seriously to see if I need Apache in my servers.) Mmm. Not completely. It depends on *what* your production load is. Don't make performance assumptions unless you are quite familiar with your application's needs and your users' profiles. -austin [/QUOTE]