Here’s what Heroku says about dyno memory usage: Dynos are available in 1X or 2X sizes and are allocated 512MB or 1024MB respectively. Dynos whose processes exceed their memory quota are identified by an R14 error in the logs. This doesn’t terminate the process, but it does warn of deteriorating application conditions: memory used above quota will swap out to disk, which substantially degrades dyno performance. If the memory size keeps growing until it reaches three times its quota, the dyno manager will restart your dyno with an R15 error.
SUMMARY: This is a step-by-step overview of how to get Oink installed in your Rails app on Heroku, and use it to analyze your memory usage. Starts with a brief description of the problem space, skip down if you just want to get on with your Oink integration. My stack includes these technologies: Rails 3, Unicorn, NewRelic, Heroku, Hodel3000CompliantLogger, and now Oink. Why is understanding memory usage important? For me, it’s because Heroku routes traffic to my dynos randomly.
From https://stripe.com/blog/stripe-checkout: It’s unfortunate that everyone has to reinvent the wheel when the time comes to implement a payments UI. We decided to build something that you can just drop in as a single tag The script tag creates a “buy” button on your page. Clicking the button pops a modal payment form where the customer submits their info directly to stripe. It’s a literally a 30 second integration. But here’s the kicker:
1 min read
I don’t know the purpose of a rant about a hosting provider except to vent my own frustrations, so I’ll keep this quick. Here’s a step-by-step list of the reasons this blog is not on Bluehost: During checkout, I was never shown a total amount for my order - just a monthly price. It wasn’t clear whether I would be paying up front or be charged monthly. I left a field empty, and when the page reloaded to ask me to fix it, I was also switched back to the most expensive hosting plan.