http://yellowlab.com.au/blog/2009/08/19/what-a-modern-rails-application-looks-like-in-production/ Tue, 1 Sep 2009 00:45:50 +1000 http://wordpress.org/?v=2.8.6 hourly 1 http://yellowlab.com.au/blog/2009/08/19/what-a-modern-rails-application-looks-like-in-production/comment-page-1/#comment-216 mark.mansour Tue, 01 Sep 2009 00:45:50 +0000 http://yellowlab.com.au/blog/?p=112#comment-216 The Yellow Lab site doesn't have the same traffic profile as the main yellow site. Rails comes with some very basic caching out of the box (i.e. if the same db query is done twice in the same request/response cycle) but aside from that we are running without any caching. The Yellow Lab site doesn’t have the same traffic profile as the main yellow site. Rails comes with some very basic caching out of the box (i.e. if the same db query is done twice in the same request/response cycle) but aside from that we are running without any caching.

]]> http://yellowlab.com.au/blog/2009/08/19/what-a-modern-rails-application-looks-like-in-production/comment-page-1/#comment-199 Alistair Mon, 24 Aug 2009 03:45:10 +0000 http://yellowlab.com.au/blog/?p=112#comment-199 What sort of strategy have you or are you planning on using for caching? Due to the fact that the profile for Yellow would be massively read heavy with limited write activity, are you planning on using a HTTP cache (nginx, squid, hardware, ..) or do you intend to keep it quite fluid by using a memory cache or some sort? What sort of strategy have you or are you planning on using for caching? Due to the fact that the profile for Yellow would be massively read heavy with limited write activity, are you planning on using a HTTP cache (nginx, squid, hardware, ..) or do you intend to keep it quite fluid by using a memory cache or some sort?

]]>