From: David Heinemeier Hansson Date: 2004-08-20T02:21:14+09:00 Subject: Re: [RAILS] way too slow... > I'm not necessarily looking for the best benchmarks, but I would > expect better than 1 req/sec. Are you running in CGI mode? If so, 1 req/sec is similar to what I'm getting. Rails does a ton of fancy, smancy stuff at startup to get all the magic poofing. In a production environment, though, this initialization cost is never seen by the users as it only happens once when a new Apache or FCGI process starts up. So I wouldn't get my hopes up for that to improve. I find 1 req/sec perfectly acceptable for developing on my Powerbook offline. I developed the new release of Basecamp like that. But even if it is a problem for you, it's pretty easy to switch between FCGI and CGI. So just use CGI when you're changing stuff all the time (like working on a single page), then use FCGI (or mod_ruby) when you need to test a bunch of pages. Also, compare this to any compiled language. Do you still think 1 second to compile all of Rails and your entire application is a raw deal? I think it's pretty darn well amazing. There's no build script to wait for. There's no file-based code generation. I find Rails development to be extremely fast compared to most other environments. I guess it's about expectations. If you're comparing to changing a line in a static HTML file and reloading, then yes, Rails is dog slow. If you're comparing to other web-application frameworks, Rails is a bonefied sprinter. > What I was really asking was if anyone had any idea *WHY* it was > running so slowly. I hope I've been able to explain that here. If not, please don't refrain from phrasing another question. -- David Heinemeier Hansson, http://www.rubyonrails.org/ -- Web-application framework for Ruby http://www.instiki.org/ -- A No-Step-Three Wiki in Ruby http://www.basecamphq.com/ -- Web-based Project Management http://www.loudthinking.com/ -- Broadcasting Brain http://www.nextangle.com/ -- Development & Consulting Services