Mercurial > rsstweet
comparison config/puma.rb @ 254:89f6c0016bab default tip
Update to latest rails
author | nanaya <me@nanaya.net> |
---|---|
date | Tue, 03 Sep 2024 19:21:25 +0900 |
parents | d5a0d66ee457 |
children |
comparison
equal
deleted
inserted
replaced
253:d726e8b92dd1 | 254:89f6c0016bab |
---|---|
1 # Puma can serve each request in a thread from an internal thread pool. | 1 # This configuration file will be evaluated by Puma. The top-level methods that |
2 # The `threads` method setting takes two numbers a minimum and maximum. | 2 # are invoked here are part of Puma's configuration DSL. For more information |
3 # Any libraries that use thread pools should be configured to match | 3 # about methods provided by the DSL, see https://puma.io/puma/Puma/DSL.html. |
4 # the maximum value specified for Puma. Default is set to 5 threads for minimum | 4 |
5 # and maximum, this matches the default thread size of Active Record. | 5 # Puma starts a configurable number of processes (workers) and each process |
6 # serves each request in a thread from an internal thread pool. | |
6 # | 7 # |
7 threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }.to_i | 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. | |
11 # | |
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) | |
8 threads threads_count, threads_count | 24 threads threads_count, threads_count |
9 | 25 |
10 # Specifies the `port` that Puma will listen on to receive requests, default is 3000. | 26 # Specifies the `port` that Puma will listen on to receive requests; default is 3000. |
11 # | 27 port ENV.fetch("PORT", 3000) |
12 port ENV.fetch("PORT") { 3000 } | |
13 | 28 |
14 # Specifies the `environment` that Puma will run in. | 29 # Allow puma to be restarted by `bin/rails restart` command. |
15 # | 30 plugin :tmp_restart |
16 environment ENV.fetch("RAILS_ENV") { "development" } | |
17 | 31 |
18 # Specifies the number of `workers` to boot in clustered mode. | 32 # Specify the PID file. Defaults to tmp/pids/server.pid in development. |
19 # Workers are forked webserver processes. If using threads and workers together | 33 # In other environments, only set the PID file if requested. |
20 # the concurrency of the application would be max `threads` * `workers`. | 34 pidfile ENV["PIDFILE"] if ENV["PIDFILE"] |
21 # Workers do not work on JRuby or Windows (both of which do not support | |
22 # processes). | |
23 # | |
24 # workers ENV.fetch("WEB_CONCURRENCY") { 2 } | |
25 | |
26 # Use the `preload_app!` method when specifying a `workers` number. | |
27 # This directive tells Puma to first boot the application and load code | |
28 # before forking the application. This takes advantage of Copy On Write | |
29 # process behavior so workers use less memory. If you use this option | |
30 # you need to make sure to reconnect any threads in the `on_worker_boot` | |
31 # block. | |
32 # | |
33 # preload_app! | |
34 | |
35 # The code in the `on_worker_boot` will be called if you are using | |
36 # clustered mode by specifying a number of `workers`. After each worker | |
37 # process is booted this block will be run, if you are using `preload_app!` | |
38 # option you will want to use this block to reconnect to any threads | |
39 # or connections that may have been created at application boot, Ruby | |
40 # cannot share connections between processes. | |
41 # | |
42 # on_worker_boot do | |
43 # ActiveRecord::Base.establish_connection if defined?(ActiveRecord) | |
44 # end | |
45 | |
46 # Allow puma to be restarted by `rails restart` command. | |
47 plugin :tmp_restart |