It's exactly the problem! How did they corrected this issue?
On Oct 12, 3:03 pm, Aldric Giacomoni <rails-mailing-l...@andreas-
s.net> wrote:
> Ilan Berci wrote:
> > Mauricio Szabo wrote:
> >> About 100 matters. Also, there is no way I can scope the query (but,
> >> with about 100 matters, I hardly think this is an issue).
>
> >> On Oct 11, 8:55 pm, Ilan Berci <[email protected]>
>
> > So either keep the matters in cache or load them up on application start
> > and keep them around in memory.. You don't need to get the matters on
> > each request if you believe that is where the bottleneck lies..
>
> > ilan
>
> To make life a little clearer, a 'matter' is a "subject" or a "topic"
> for a course.. The bottleneck is that the students all want their first
> choice classes so there's a ridiculous amount of connections being made
> and it's overloading the web server.
> I think.
> And I only think that because this happened in my college when they
> implemented online course selection.
> --
> 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
-~----------~----~----~----~------~----~------~--~---
