+1 On Thu, Apr 28, 2011 at 5:42 PM, Mark Ranallo <[email protected]> wrote: > Along the lines of what Ben is suggesting, I would run a performance test of > just ruby code on each box. This can give you a kind of baseline for > performance difference between platforms. If that runs as expected then > move on to the rails stack. > > On Thursday, April 28, 2011 at 5:29 PM, Ben Hughes wrote: > > One thing you'll also want to do, if you aren't already, is isolate any > potential issues relating to the rails environment. > So, if it's running well in the "development" environment locally, run it on > the slices in the same "development" environment. While typically the only > difference of note is "cache_classes" (which should produce opposite > behavior - much faster when deployed with cache_classes set to true), there > may be other things depending on your code that is causing differences > dependent on the Rails environment, or something quirky relating to your > code and cache_classes. > > On Thu, Apr 28, 2011 at 4:49 PM, Guyren Howe <[email protected]> wrote: > > On Apr 28, 2011, at 4:44 PM, Chris Corriveau wrote: > >> Same result with 3 different slices? > > Indeed. > > -- > 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
-- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
