tag:blogger.com,1999:blog-4704664917418794835.post8236105658793522179..comments2023-07-01T05:41:30.469-07:00Comments on Headius: JRuby on Rails on Amazon Elastic Beanstalkheadiushttp://www.blogger.com/profile/15717357218364947795noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4704664917418794835.post-78965336358139216212012-07-17T23:26:00.197-07:002012-07-17T23:26:00.197-07:00Hi Charles,
Thanks doing this write up. Sorry fo...Hi Charles,<br /><br />Thanks doing this write up. Sorry for this noob question...but I'm wondering how do you do rake tasks on the instance generated by the Elastic Beanstalk. Am I just totally off? I just wanted to run 'rake db:create' and 'rake db:migrate'. I ssh'd in and can't find app root directory is. Maybe things are different with jRuby? Sorry, but I'm just super confused right now.<br /><br />Thanks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4704664917418794835.post-21389148928764987622011-01-19T16:32:42.317-08:002011-01-19T16:32:42.317-08:00Hi Just a quick question for someone who is only f...Hi <br><br>Just a quick question for someone who is only familiar with Heroku<br><br>When you say the small memory might not be suited to an app "with many Rails instances"... what does that mean?<br><br>I was assuming an AWS micro server would be a single Rails app (in a similar way as a Heroku dyno)<br><br>So.... the small memory would be ok if we only intended on running one instance per Micro server?<br><br>It would still be half the price of Heroku?<br><br>Am I thinking about this the right way?<br><br>I am not sure how these instances get glued together, in a way that Heroku does for dynos automatically.<br><br>Also, I think Heroku's Varnish layer might make it potentially far more economical still ?<br><br>Just mu (novice) thoughts<br><br>thanksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4704664917418794835.post-65604304516221726952011-01-19T17:18:24.239-08:002011-01-19T17:18:24.239-08:00Anonymous: The micro instance definitely does *wor...Anonymous: The micro instance definitely does *work* for small, single-instance apps, but in my experience even for the smallest apps they throttle CPU use too heavily for it to be useful. But that's what you get for a free instance (micro is free).<br><br>When deploying JRuby, a single process is your entire app on that machine; JRuby can either route all requests through a single instance ("threadsafe" mode) or spin up multiple copies of your app in-memory (like a cluster-in-a-can). In the latter case, micro instances would be too tightly constrained to run an app that has more than one instance, but might be ok for a single-instance or threadsafe setup.<br><br>As far as elastically scaling, once you're hitting the limits of a given server instance, I believe AWSEB will spin up additional instances for you.<br><br>And of course, there's the benefit that your're running JRuby, which Heroku does not support.Charles Oliver Nutterhttp://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-4704664917418794835.post-71701888829332304672011-01-19T22:27:26.371-08:002011-01-19T22:27:26.371-08:00Interesting! Slow deployment doesn't sound too...Interesting! Slow deployment doesn't sound too inviting though. I also wonder how this compares to Heroku performancewise. Never used JRuby before. I might make some tests...Niconoreply@blogger.comtag:blogger.com,1999:blog-4704664917418794835.post-36533700063101579752011-01-21T06:44:56.885-08:002011-01-21T06:44:56.885-08:00Hey cool, this is exactly what I was thinking abou...Hey cool, this is exactly what I was thinking about this morning. And of course my generous friend Denton Gentry pointed me to this post after a half formed tweet.<br><br>Any big spin up, delays? One of things I wasn't too crazy about on app engine with jruby was the slow vm, warmup thingy (my rough apps are slow enough).<br><br>Hope all is well in jruby land. Look forward to faster, broader, more compatible and seductive jruby.Mark Esselhttp://www.blogger.com/profile/02148726313106222507noreply@blogger.com