A very simple solution would be to just have the system output static html. This would scale infinite :) Why worry about caching when you can do even better by just serving static html. "SEan Wolfe" <nospam / nowhere.com> wrote in message news:11j90hjesob623e / news.supernews.com... >I have an upcoming project that is for a news site with daily and hourly >content updates. Currently everything is done by static HTML. Obviously >it's a lot of work to get their stuff up there. > > I've had a great time working in Ruby and Rails of rother web projects. > But I'm just wondering if it's possible to do large scale sites with RoR. > > The site needs to be able to handle a minimum of 200 req/sec. I'd figure > RoR, with a proper caching configuration, and maybe Squid in front to do > some short term page caching could possibly handle the project, but I've > never used RoR for anything this large. It' might be possible since most > of the site doen't need to keep a user state, since it's only news pages, > no logins (except for the writers/editors which is a small fraction of the > traffic). > > Has anyone had any success running sites this large or larger with RoR? If > so, were there any special requirements you needed to get it running? Were > more than one server needed for such applications? What were the machine > specs? > > Thanks for anyone's input. > > Sean