bill walton wrote: > On Thu, 2009-08-06 at 22:42 +0200, Alpha Blue wrote: >> For readability, this is better to look at: >> >> http://pastie.org/574570 > > Are you already using Memcached? If not, you'll want to. Your data > doesn't change very often, so one strategy you might consider is kicking > off a job that runs your queries in the 'wee hours' of the morning-after > so they're cached for your users. > > HTH, > Bill
Hi Bill, thanks for the response mate. I haven't checked out memcached and will go look at that now. The problem for running my queries is that there are 120 teams so that would mean approximately 14,400 quries since any two teams can be matched up and compared to one another. I'm not sure that would work. Even without any type of stoppage time, I'm probably looking at around 90 minutes to run all those queries? Maybe I can do something like that. Without optimization (can't quite think of anything further I can do to optimize it (unless memcached will work) - the only thing further I think that would help would be a multi-tiered server setup with the database sitting on a server by itself and using nginx as a front end on another server and my content on yet another server. I've been contemplating this but right now it would be fairly expensive and I don't have enough time to implement it before the start of this season. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
