I would agree with Kevin. You're likely swapping pretty quick with only 512MB on the machine, especially if you're expecting to return 3500 rows -- did you try a larger slice?
Try running `free -m` on the slice to see your current memory state while that monster query is running. On Fri, Apr 29, 2011 at 1:56 PM, Kevin Ball <[email protected]> wrote: > Sounds like memory allocation as it is instantiating the ActiveRecord > objects to me. How much memory do you have on the slice vs the other system > that isn't having trouble? > > -Kevin > > > On Fri, Apr 29, 2011 at 1:51 PM, Guyren Howe <[email protected]> wrote: > >> I’ve somewhat pinned down where my slowdown (see previous topic) is >> happening. >> >> I’m doing a query (which is scoped/lazy in Rails 3) with two joins and a >> couple of simple conditions on the first and one of the join tables. >> >> This executes just fine and comes back with about 3,500 rows. >> >> At this point, Rails pauses approximately forever somewhere in the bowels >> of ActiveRecord. >> >> -- >> SD Ruby mailing list >> [email protected] >> http://groups.google.com/group/sdruby > > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
