sutty/config/puma.rb

65 lines
2.5 KiB
Ruby
Raw Normal View History

2019-03-26 15:32:20 +00:00
# frozen_string_literal: true
2018-01-02 17:19:25 +00:00
# Puma can serve each request in a thread from an internal thread pool.
# The `threads` method setting takes two numbers: a minimum and maximum.
2019-08-29 17:54:19 +00:00
# Any libraries that use thread pools should be configured to match the
# maximum value specified for Puma. Default is set to 5 threads for
# minimum and maximum; this matches the default thread size of Active
# Record.
2018-01-02 17:19:25 +00:00
#
2019-03-26 15:32:20 +00:00
threads_count = ENV.fetch('RAILS_MAX_THREADS') { 1 }
2018-01-02 17:19:25 +00:00
threads threads_count, threads_count
2019-08-29 17:54:19 +00:00
# Specifies the `port` that Puma will listen on to receive requests;
# default is 3000.
2018-01-02 17:19:25 +00:00
#
2019-03-26 15:32:20 +00:00
port ENV.fetch('PORT') { 3000 }
2018-01-02 17:19:25 +00:00
# Specifies the `environment` that Puma will run in.
#
2019-03-26 15:32:20 +00:00
environment ENV.fetch('RAILS_ENV') { 'development' }
2018-01-02 17:19:25 +00:00
2019-08-29 17:54:19 +00:00
# Specifies the number of `workers` to boot in clustered mode. Workers
# are forked webserver processes. If using threads and workers together
2018-01-02 17:19:25 +00:00
# the concurrency of the application would be max `threads` * `workers`.
# Workers do not work on JRuby or Windows (both of which do not support
# processes).
#
2019-04-08 18:31:29 +00:00
workers ENV.fetch('WEB_CONCURRENCY') { 2 }
2018-01-02 17:19:25 +00:00
# Use the `preload_app!` method when specifying a `workers` number.
# This directive tells Puma to first boot the application and load code
# before forking the application. This takes advantage of Copy On Write
2019-08-29 17:54:19 +00:00
# process behavior so workers use less memory.
2018-01-02 17:19:25 +00:00
#
2019-04-08 18:31:29 +00:00
preload_app!
2018-01-02 17:19:25 +00:00
# Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart
2019-04-08 18:31:29 +00:00
pidfile 'tmp/puma.pid'
2019-11-16 23:13:30 +00:00
# If you are preloading your application and using Active Record, it's
# recommended that you close any connections to the database before workers
# are forked to prevent connection leakage.
#
before_fork do
ActiveRecord::Base.connection_pool.disconnect! if defined?(ActiveRecord)
end
# The code in the `on_worker_boot` will be called if you are using
# clustered mode by specifying a number of `workers`. After each worker
# process is booted, this block will be run. If you are using the `preload_app!`
# option, you will want to use this block to reconnect to any threads
# or connections that may have been created at application boot, as Ruby
# cannot share connections between processes.
#
on_worker_boot do
ActiveRecord::Base.establish_connection if defined?(ActiveRecord)
2020-09-18 23:51:52 +00:00
require 'prometheus_exporter/instrumentation'
PrometheusExporter::Instrumentation::ActiveRecord.start(custom_labels: { type: 'puma_worker' }, config_labels: %i[database host])
PrometheusExporter::Instrumentation::Puma.start
PrometheusExporter::Instrumentation::Process.start(type: 'web')
2019-11-16 23:13:30 +00:00
end