Wow.. from 1.2.3 to 3.0.7? That is pretty extreme. Firstly I am really surprised that it still runs..
Im sure your log will be full of deprecation stuff, so my guess would be not to wait for 3.2 but instead start now to go through your application and see what is deprecated. Just scopes as an example have changed a lot, so I would say check your application first. Also if I am not sure if lighttpd supports streaming, I wouldnt think so, so in the long run you will probably be better off swapping to unicorn+nginx or something similar. regards stefano On Jul 26, 10:23 am, hideto <[email protected]> wrote: > I just upgraded my application infrastructure to Rails 3.0.7 from > Rails 1.2.3. > > After performance test, I found: > 1. 15% downgrade time cost per request > 2. 200% memory cost per process > > I'm using lighttpd/fastcgi/rubyee. > > I found that Rails 3.2 will improve performance & memory cost. > Where can I find the roadmap of Rails 3.2 and when will Rails 3.2 > release? > Is there any workaround for short-term? -- 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.
