I'd say standardize on a deployment model that leverages lots of nuts and bolts ruby doesn't care about.

Specifically, try using the apr (apache portable runtime), or leverage tomcat (which can use apr) + jruby + jndi jdbc connection pools.

Let rails be rails, your best bet for performance is either making the underlying ruby runtime better or leveraging things that are designed to be high performance.