<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Heroku - Tag - MC Squared</title><link>https://mc-squared.dev/tags/heroku/</link><description>Heroku - Tag - MC Squared</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Fri, 12 Jun 2020 09:00:01 +1200</lastBuildDate><atom:link href="https://mc-squared.dev/tags/heroku/" rel="self" type="application/rss+xml"/><item><title>Preparing a Heroku Application for Production</title><link>https://mc-squared.dev/2020/06/preparing-a-heroku-app-for-production/</link><pubDate>Fri, 12 Jun 2020 09:00:01 +1200</pubDate><author>Jonathan Miles</author><guid>https://mc-squared.dev/2020/06/preparing-a-heroku-app-for-production/</guid><description><![CDATA[<p>So you&rsquo;ve been tinkering away at your side project web app and are now ready to launch it to the world. You fire up a <a href="https://www.heroku.com" target="_blank" rel="noopener noreffer ">Heroku</a> account, push up the source code et voilà, you&rsquo;re on the internet.</p>
<p>The thing is now you&rsquo;re running in &ldquo;production&rdquo; mode, so you&rsquo;re going to want to set up some infrastructure for your application. I&rsquo;m going to be using Ruby on Rails here but the general ideas will be the same for virtually any web application on any framework.</p>]]></description></item><item><title>Heroku Hobby Postgres Performance</title><link>https://mc-squared.dev/2020/04/heroku-hobby-postgres-performance/</link><pubDate>Wed, 22 Apr 2020 09:00:00 +1200</pubDate><author>Jonathan Miles</author><guid>https://mc-squared.dev/2020/04/heroku-hobby-postgres-performance/</guid><description><![CDATA[<h2 id="performance-woes">Performance Woes</h2>
<p>I&rsquo;ve been running <a href="https://gitarborist.com" target="_blank" rel="noopener noreffer ">GitArborist</a> for a couple of months now, gradually adding features. Like any good production app, I have some logging and metrics set up to monitor and troubleshoot issues.</p>
<p>Over these last few months, I&rsquo;ve seen recurring performance issues, with <strong>response times in double-digit seconds</strong> in some cases. I made various fixes like you&rsquo;d expect: adding database indexes, returning early where possible, etc. These were improvements to be sure, but I never fully removed these occasional long response times, though I could not reproduce it myself.</p>]]></description></item></channel></rss>