If the system slows down because of the amount of users you will need more horsepower or limit the amount of concurrent users that use the system. In apache you can set the MaxClients setting if you are using a worker MPM. But you need to find where the bottleneck is so that you can fix it.
I like to start with the database first. Tune the database to the max then look at rails then if you still have issues start limiting at Apache or upgrade/add servers. On Oct 9, 8:48 am, sax <[email protected]> wrote: > There's a great screencast series named "Scaling Rails" that may give > you ideas. > > But yeah, as the previous poster implies, your problem could be > anywhere. You may want to try to identify where the main bottleneck is > in your application (whether it's the rails server or the db server) > and how you can optimize your code or your deployment to reduce the > load. > > On Oct 9, 7:38 am, Ilan Berci <[email protected]> > wrote: > > > > > Maurício Szabo wrote: > > > > How to protect against these cases? > > > > Thanks in advance, > > > Mauricio > > > Advise administration that they will need to cut down on the number of > > students they enroll each year. > > > It that doesn't appeal to you, then please resubmit your post with a > > little more information including but not limited to caching details, > > profile results, cluster design, deployment(s), memcache, etc.. > > > hth > > > ilan > > > -- > > Posted viahttp://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 -~----------~----~----~----~------~----~------~--~---
