You can easily get your APEX back up without blaming Ruby. There is nothing inherent to Ruby that should stop you from doing that. More likely than not you pro

You can easily get your APEX back up without blaming Ruby. There is nothing inherent to Ruby that should stop you from doing that. More likely than not you probably have a couple nasty requests that should be handled by a background task and a few more or less caching calls. Additionally, from your user's perspective, 300~ish ms is already pretty good, I wouldn't worry about that too much. You use Ruby on Rails because it is speed on speed for rolling out features. Focus on a better user experience with pretty good performance and you guys will be alright.