Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We've had issues like this with Unicorn for some time . . . we also get seemingly random timeout errors, even though we never see much load and have 4 dynos with 4 workers each (we never have any request queuing). We have had 0 luck getting rid of these errors, even with help from Heroku. I get the feeling even they aren't 100% confident in the optimal settings for Unicorn on Heroku.</p> <p>We just recently switched to Puma and so far so good, much better performance and no weird timeouts yet. One of the other reasons we switched to Puma is that I suspect some of our random timeouts come from "slow clients" . . . Unicorn isn't designed to handle slow clients.</p> <p>I will let you know if we see continued success with Puma, but so far so good. The switch is pretty painless, assuming your app is thread-safe.</p> <p>Here are the puma settings we are using. We are using "Clustered Mode".</p> <p>procfile:</p> <pre><code>web: bundle exec puma -p $PORT -C ./config/puma.rb </code></pre> <p>puma.rb:</p> <pre><code>environment ENV['RACK_ENV'] threads Integer(ENV["PUMA_THREADS"] || 5),Integer(ENV["PUMA_THREADS"] || 5) workers Integer(ENV["WEB_CONCURRENCY"] || 4) preload_app! on_worker_boot do ActiveSupport.on_load(:active_record) do ActiveRecord::Base.establish_connection end end </code></pre> <p>We currently have <code>WEB_CONCURRENCY</code> set to 4 and <code>PUMA_THREADS</code> set to 5.</p> <p>We aren't using an initializer for DB_POOL, just using the default DB_POOL setting of 5 (hence the 5 threads).</p> <p>The only reason we are using <code>WEB_CONCURRENCY</code> as our environment variable name is so that log2viz reports the correct number of workers. Would rather call it <code>PUMA_WORKERS</code> but whatever, not a huge deal.</p> <p>Hope this helps . . . again, will let you know if we see any issues with Puma.</p>
    singulars
    1. This table or related slice is empty.
    1. POError R12 (Exit timeout) using Heroku's recommended Unicorn config
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USbcb
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhen we launched our product we were just using straight RACK for 3 months. There were no issues. I decided to upgrade to Unicorn for better scalability and immediately stated seeing timeouts and memory warnings. I spent 2 weeks fine tuning everything... All assets come form a CDN, are precompiled before deployment, checked the gems, profiled for memory leaks against production database, cached almost everything and the app still throws these errors from Logentries. So like bcb says, I think they just happen sometimes.
      singulars
      1. PO
      1. USCarlos Cervantes
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload