mirror of
https://github.com/manyfold3d/manyfold.git
synced 2026-10-22 19:52:18 -05:00
73 lines
3.1 KiB
Ruby
73 lines
3.1 KiB
Ruby
# This configuration file will be evaluated by Puma. The top-level methods that
|
|
# are invoked here are part of Puma's configuration DSL. For more information
|
|
# about methods provided by the DSL, see https://puma.io/puma/Puma/DSL.html.
|
|
#
|
|
# Puma starts a configurable number of processes (workers) and each process
|
|
# serves each request in a thread from an internal thread pool.
|
|
#
|
|
# You can control the number of workers using ENV["WEB_CONCURRENCY"]. You
|
|
# should only set this value when you want to run 2 or more workers. The
|
|
# default is already 1.
|
|
#
|
|
workers ENV.fetch("WEB_CONCURRENCY", 4)
|
|
preload_app!
|
|
|
|
# The ideal number of threads per worker depends both on how much time the
|
|
# application spends waiting for IO operations and on how much you wish to
|
|
# prioritize throughput over latency.
|
|
#
|
|
# As a rule of thumb, increasing the number of threads will increase how much
|
|
# traffic a given process can handle (throughput), but due to CRuby's
|
|
# Global VM Lock (GVL) it has diminishing returns and will degrade the
|
|
# response time (latency) of the application.
|
|
#
|
|
# The default is set to 3 threads as it's deemed a decent compromise between
|
|
# throughput and latency for the average Rails application.
|
|
#
|
|
# Any libraries that use a connection pool or another resource pool should
|
|
# be configured to provide at least as many connections as the number of
|
|
# threads. This includes Active Record's `pool` parameter in `database.yml`.
|
|
#
|
|
max_threads_count = ENV.fetch("RAILS_MAX_THREADS", 16)
|
|
min_threads_count = ENV.fetch("RAILS_MIN_THREADS", 4)
|
|
threads min_threads_count, max_threads_count
|
|
|
|
# Specifies the `worker_timeout` threshold that Puma will use to wait before
|
|
# terminating a worker in development environments.
|
|
#
|
|
worker_timeout 3600 if ENV.fetch("RAILS_ENV", "development") == "development"
|
|
|
|
# Specifies the `port` that Puma will listen on to receive requests; default is 3000.
|
|
# Support IPv6 by binding to host `::` instead of `0.0.0.0`
|
|
port(ENV.fetch("PORT", 3000), "::")
|
|
|
|
# Specifies the `environment` that Puma will run in.
|
|
#
|
|
environment ENV.fetch("RAILS_ENV") { "development" }
|
|
|
|
# Specifies the `pidfile` that Puma will use.
|
|
pidfile ENV.fetch("PIDFILE") { "tmp/pids/server.pid" }
|
|
|
|
# Specifies the number of `workers` to boot in clustered mode.
|
|
# Workers are forked web server processes. If using threads and workers together
|
|
# 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).
|
|
workers ENV.fetch("WEB_CONCURRENCY", 4)
|
|
|
|
# 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
|
|
# process behavior so workers use less memory.
|
|
preload_app!
|
|
|
|
# Allow puma to be restarted by `rails restart` command.
|
|
plugin :tmp_restart
|
|
|
|
# Run the Solid Queue supervisor inside of Puma for single-server deployments
|
|
plugin :solid_queue if ENV["SOLID_QUEUE_IN_PUMA"]
|
|
|
|
# Specify the PID file. Defaults to tmp/pids/server.pid in development.
|
|
# In other environments, only set the PID file if requested.
|
|
pidfile ENV["PIDFILE"] if ENV["PIDFILE"]
|