# Is Ruby suitable to develop a large dynamic web site with a heavy database usage? **URL:** \ **Category:** Ruby\ **Created:** [December 18, 2007, 5:05am UTC](https://www.ruby-forum.com/t/is-ruby-suitable-to-develop-a-large-dynamic-web-site-with-a-heavy-database-usage/123484 "2007-12-18T05:05:23Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tenxian](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tenxian](https://www.ruby-forum.com/u/tenxian)\ **Post date:** [December 18, 2007, 5:05am UTC](https://www.ruby-forum.com/t/is-ruby-suitable-to-develop-a-large-dynamic-web-site-with-a-heavy-database-usage/123484/1 "2007-12-18T05:05:23Z")
How about its running speed? ---
**Author:** ![tenxian](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tenxian](https://www.ruby-forum.com/u/tenxian)\ **Post date:** [December 18, 2007, 5:21am UTC](https://www.ruby-forum.com/t/is-ruby-suitable-to-develop-a-large-dynamic-web-site-with-a-heavy-database-usage/123484/2 "2007-12-18T05:21:45Z")
On Dec 18, 12:58 am, tenxian [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > How about its running speed? I don’t want to sounds harsh, but if you research a bit (I mean, google) you will find pretty much all the answers to your questions. Ruby speed, Rails as possible framework. Concurrency, hardware or VPS to deploy into (specialized rails/ruby hosting companies). Also look at RubyCorner and read most posts from Ruby blogs. Don’t forget to actually try something in ruby before choosing it as platform, in that way, you can know the pros and cons of it beforehand. HTH, Luis L. ---
**Author:** ![tenxian](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tenxian](https://www.ruby-forum.com/u/tenxian)\ **Post date:** [December 18, 2007, 5:39am UTC](https://www.ruby-forum.com/t/is-ruby-suitable-to-develop-a-large-dynamic-web-site-with-a-heavy-database-usage/123484/3 "2007-12-18T05:39:51Z")
tenxian wrote: > How about its running speed well, there are sites talking about speeding it up. and there is MERB, that speeds up the actionpak. there is a whole google wanna-be site on ruby/rails, and they say the apple mini and mongrel just rock. then some say cache the whole freaking thing. google, and there is stuff, and good stuff, and bad stuff, and old stuff, more old stuff. lol ---
**Author:** ![tenxian](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tenxian](https://www.ruby-forum.com/u/tenxian)\ **Post date:** [December 23, 2007, 9:36pm UTC](https://www.ruby-forum.com/t/is-ruby-suitable-to-develop-a-large-dynamic-web-site-with-a-heavy-database-usage/123484/4 "2007-12-23T21:36:12Z")
Hi, Am Dienstag, 18. Dez 2007, 13:00:17 +0900 schrieb tenxian: > How about its running speed? I never did measure it in any way but at least I can say that FastCGI is worth being considered as it is very easy to implement. I even wrote my own one. You may have a look at it if you like. Bertram ---
**Author:** ![tenxian](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tenxian](https://www.ruby-forum.com/u/tenxian)\ **Post date:** [December 23, 2007, 5:46pm UTC](https://www.ruby-forum.com/t/is-ruby-suitable-to-develop-a-large-dynamic-web-site-with-a-heavy-database-usage/123484/5 "2007-12-23T17:46:21Z")
On Tue, 18 Dec 2007, tenxian wrote: > How about its running speed? The short answer to the question in the subject is: Absolutely. The overall execution speed is less likely to be a bottleneck on a site with heavy db usage because the db, in that scenario, often becomes the bottleneck. However, to address the basic issue of running speed, I have sites running on Ruby 1.8.x that are completely dynamically rendered, with all content coming out of the database, and everything, including the navigation, constucted dynamically based on the db content. These sites are running on a 100% ruby based stack (no Apache, lighttpd, nginx, etc… involved), and can do on the order of 1100 dynamically created page views per second through a single backend process. A cluster of three backend processes does around 2700-2800 r/s. I get those speeds because I don’t go back into the database itself on every request, so they serve to illustrate what kind of performance a person can get when the bottleneck is NOT the database. Ruby speed shouldn’t be a problem when addressing the scalability of a large dynamic web site. Kirk H.