On Nov 30, 3:28 am, BW <[email protected]> wrote: > Fred, > > I'm using the default, the CookieStore. >
That's fine. I ran into an issue because of a database store that wasn't activerecord store. The issue was that the session store wasn't returning connections to the connection pool, so after a few normal page loads all of the connections are marked as busy and you start having to wait for timeouts before subsequent actions can get a database connection. If this is the problem then reducing wait_timeout or increasing the pool size (in database.yml - see http://rubyclub.com.ua/doc/api-rails-2.2/classes/ActiveRecord/ConnectionAdapters/ConnectionPool.html) will delay the onset of the problem (this isn't a fix though - you need to find what is leaking connections) Fred > On Mon, Nov 30, 2009 at 3:53 AM, Frederick Cheung < > > > > [email protected]> wrote: > > > On Nov 29, 6:58 pm, BW <[email protected]> wrote: > > > I'm finally upgrading one of my apps to Rails 2.3.5 from 2.1. One thing > > > I've noticed is that I'm getting terrible performance with MySQL under > > Rails > > > 2.3. The 2.3 version runs 10x slower than the 2.1 version. Same > > database, > > > almost the same code, different version of Rails. > > > what session store are you using ? > > > Fred -- 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.
