Its fair to make an assumption that the database could be a bottleneck when you use the limited hobby plan. There are likely some optimizations you can do to help improve connection pooling regardless ( like code below). However when this is truly the bottleneck, you would expect to find timeouts occuring often, not just slowness. In order to get a better sense of where your issues lie, I recommend adding the NewRelic plugin next.
The NewRelic Stark plan (recommended) - or the Wayne plan ( a bit too limited in my opinion) is free and will help visualize you Apps performance and trace Errors. You will likely find that dyno queuing time and memory consumption is contributing to the slowness you are getting, and there are a few ways this could improve without ever messing with database connections. Improving your code response time and limiting your database hits (via caching) are good areas to investigate.
With that said, I do recommend adding the following code to your unicorn file as described in the article you mention.
after_fork do |server, worker|
Signal.trap 'TERM' do
puts 'Unicorn worker intercepting TERM and doing nothing. Wait for master to sent QUIT'
end
# other settings
if defined?(ActiveRecord::Base)
config = ActiveRecord::Base.configurations[Rails.env] ||
Rails.application.config.database_configuration[Rails.env]
config['reaping_frequency'] = ENV['DB_REAP_FREQ'] || 10 # seconds
config['pool'] = ENV['DB_POOL'] || 2
ActiveRecord::Base.establish_connection(config)
end
end