|
254
|
1 # This configuration file will be evaluated by Puma. The top-level methods that
|
|
|
2 # are invoked here are part of Puma's configuration DSL. For more information
|
|
|
3 # about methods provided by the DSL, see https://puma.io/puma/Puma/DSL.html.
|
|
|
4
|
|
|
5 # Puma starts a configurable number of processes (workers) and each process
|
|
|
6 # serves each request in a thread from an internal thread pool.
|
|
|
7 #
|
|
|
8 # The ideal number of threads per worker depends both on how much time the
|
|
|
9 # application spends waiting for IO operations and on how much you wish to
|
|
|
10 # to prioritize throughput over latency.
|
|
89
|
11 #
|
|
254
|
12 # As a rule of thumb, increasing the number of threads will increase how much
|
|
|
13 # traffic a given process can handle (throughput), but due to CRuby's
|
|
|
14 # Global VM Lock (GVL) it has diminishing returns and will degrade the
|
|
|
15 # response time (latency) of the application.
|
|
|
16 #
|
|
|
17 # The default is set to 3 threads as it's deemed a decent compromise between
|
|
|
18 # throughput and latency for the average Rails application.
|
|
|
19 #
|
|
|
20 # Any libraries that use a connection pool or another resource pool should
|
|
|
21 # be configured to provide at least as many connections as the number of
|
|
|
22 # threads. This includes Active Record's `pool` parameter in `database.yml`.
|
|
|
23 threads_count = ENV.fetch("RAILS_MAX_THREADS", 3)
|
|
89
|
24 threads threads_count, threads_count
|
|
|
25
|
|
254
|
26 # Specifies the `port` that Puma will listen on to receive requests; default is 3000.
|
|
|
27 port ENV.fetch("PORT", 3000)
|
|
89
|
28
|
|
254
|
29 # Allow puma to be restarted by `bin/rails restart` command.
|
|
|
30 plugin :tmp_restart
|
|
89
|
31
|
|
254
|
32 # Specify the PID file. Defaults to tmp/pids/server.pid in development.
|
|
|
33 # In other environments, only set the PID file if requested.
|
|
|
34 pidfile ENV["PIDFILE"] if ENV["PIDFILE"]
|
