anchor.diff:        Cache hit rate above 99%
       <% else %>
         Low cache hit rate
  +    <% end %>
  +  </div>
  +  <div class="alert alert-<%= @query_stats_enabled && @slow_queries.empty? ? "success" : "warning" %>">
  +    <% if !@query_stats_enabled %>
  +      Query stats must be enabled for slow queries
  +    <% elsif @slow_queries.any? %>
  +      <%= pluralize(@slow_queries.size, "slow query") %>
  +    <% else %>
  +      No slow queries
       <% end %>
     </div>
     <div class="alert alert-<%= @missing_indexes.empty? ? "success" : "warning" %>">
  
positive.code:     <%= render partial: "query_stats_table", locals: {queries: @slow_queries} %>
    </div>
  <% end %>
  
  <% if @long_running_queries.any? %>
    <div class="content">
      <h1>Long Running Queries</h1>
  
      <%= render partial: "queries_table", locals: {queries: @long_running_queries} %>
    </div>
  <% end %>
  
  <% if !@good_cache_rate %>
    <div class="content">
      <h1>Low Cache Hit Rate</h1>
  
      <p>
        Index Hit Rate: <%= (@index_hit_rate * 100).round(1) %>%
        <br />
        Table Hit Rate: <%= (@table_hit_rate * 100).round(1) %>%
      </p>
  
      <p>
        The cache hit rate <%= link_to "should be above 99%", "https://devcenter.heroku.com/articles/understanding-postgres-data-caching", target: "_blank" %> in most cases.  You can often increase this by adding more memory.
        <!-- TODO better suggestions -->
      </p>
    </div>
  <% end %>
  
  
  <% if @missing_indexes.any? %>
    <div class="content">
  
negative.code: <div id="status">
    <div class="alert alert-<%= @long_running_queries.empty? ? "success" : "warning" %>">
      <% if @long_running_queries.any? %>
        <%= pluralize(@long_running_queries.size, "long running query") %>
  