Dave Cheney wrote: >>> The staging server (also split with Xen) is set up pretty much >>> identically >>> >>> On the production box, pretty much immediately (and I'm talking about >>> within one or two requests), the mongrels climb up to about 150-160MB. >>> One the staging server, even when I'm hammering it with a benchmarking >>> suite (have tried with httperf, and bench and crawl) the mongrels sit >>> comfortably at about 60MB each. > > Your issue may be related to the amount of data in your production > database. In our codebase we're constantly be hit by AR calls that bring > the whole table into memory, then filter out the bits they don't want > rails > side. > > In development we don't notice the bloat or delay but under a production > dataset the effect was pronounced. > > Cheers > > Dave
The staging server is using a copy of the production database, so that can't be it (though I thought it might be before setting up the staging server). -- Posted via http://www.ruby-forum.com/. _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
