On Apr 29, 2011, at 2:03 PM, James Miller wrote: > 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.
I did try a 1GB slice, which made no difference whatever. I just found that removing one of the constraints — which would, if anything, give me more rows — cures the problem. So I have a workaround. But there’s an ugly issue lurking there somewhere. -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
