I think I have found the answer - sweepers! We are using a file_store and when the sweepers run on the ec2 instance it is taking forever. (like 10 seconds to rm a directory). Obviously it is time to revisit the caching!
On Dec 5, 6:48 am, "Jeffrey L. Taylor" <[email protected]> wrote: > Quoting phil <[email protected]>: > > > > > > > We have a method that is just taking a ridiculous amount of time in > > production: > > > Production: > > Completed in 84043ms (DB: 35243) | 302 Found [http://x.com/admin/x/ > > 3262/x] (pid:10052) > > > Dev: > > Completed in 268ms (DB: 201) | 302 Found [http://c.local/admin/x/3262/ > > x] (pid:27599) > > > To do this test I dumped the production database, loaded it into my > > dev environment and performed the identical task on the identical > > data. > > Our production environment is an Amazon EC2 instance, which ok is not > > as fast as my MacPro, but still! > > What size EC2 instance are you using? And what size is MacPro? A small EC2 > instance is the equivalent of a 1GHz Opteron. I'd expect it to be slower than > a 2.XGHz Quad-core. And are they running the same DB server. And is the DB > server in the same instance? My small EC2 instance is slower than my 1.6GHz > single-CPU laptop, but only 10-20%. Both are running Apache, Passenger, and > MySQL. > > I don't find significant differences between running Webrick and Apache w/ > Passenger on my laptop in terms of response times. > > Jeffrey -- 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.
