3 ms·
The commenter called dude is spot on with his comment about Heroku's marketing copy on their homepage: "Get up and running in minutes, and deploy instantly wit
by instakill 14y ago
The commenter called dude is spot on with his comment about Heroku's marketing copy on their homepage:
"Get up and running in minutes, and deploy instantly with git. Focus 100% on your code, and never think about servers, instances, or VMs again."
This is not the case anymore.
- adamwiggins 14y agoI agree that thinking about memory use steps a bit closer to the world of server administration, which doesn't thrill me. We've actually had 2X dynos in alpha for close to a year, but we never pushed forward with a public release precisely for this reason. However, the demand from customers — especially apps on the JVM — has been overwhelming. There's no way around it: once you start doing heavy background processing (e.g. geospacial or image processing) or web concurrency with a memory-intensive language like Ruby, then you care about memory. It would be very head-in-the-sand for us to not serve this need. I'd love to imagine that there's some design that allows us to abstract away memory, but despite a lot of attempts, we haven't seen one. Further, memory is generally the most expensive part of server-side computing resources these days, so decoupling memory use from price isn't very feasible.
- deleted 14y ago[deleted]