Mike Dalessio
|
550a4b7c33
|
Don't set puma performance settings in dev
|
2025-10-10 16:53:52 -04:00 |
|
Mike Dalessio
|
257aeb8511
|
GC: Defer major GC cycles until after request handling completes
|
2025-10-10 16:49:01 -04:00 |
|
Mike Dalessio
|
016f00dfb5
|
Call Process.warmup
|
2025-10-10 15:17:13 -04:00 |
|
Mike Dalessio
|
ba090196d8
|
Baseline puma worker/thread config
Because we expect fewer I/O waits than Rails apps that connect to the
database over the network, let's start with a baseline config of 1
worker per CPU, 1 thread per worker and tune it from there.
https://edgeguides.rubyonrails.org/tuning_performance_for_deployment.html#puma
|
2025-10-10 15:00:03 -04:00 |
|
Jeremy Daer
|
a798cc445c
|
Prom metrics in dev (#1269)
|
2025-10-08 14:06:28 -07:00 |
|
Mike Dalessio
|
13db361aed
|
dep: bump puma
also remove the incorrect on_worker_boot block and the needless
before_fork block
|
2025-09-15 12:31:57 -04:00 |
|
Mike Dalessio
|
f01e20f64b
|
Introduce yabeda for puma metrics
|
2025-09-15 12:08:43 -04:00 |
|
Kevin McConnell
|
8b17a33a75
|
Only run Solid Queue in Puma in dev
In production, we have extra containers for it.
|
2025-02-10 17:55:46 +00:00 |
|
Kevin McConnell
|
90538afb3b
|
Add Solid Queue
We'll run jobs via the Puma plugin for now, to simplify the deployment.
|
2025-01-08 14:02:45 +00:00 |
|
Jeffrey Hardy
|
391e11de22
|
Modernize puma configuration
|
2024-08-16 16:33:36 -04:00 |
|
Kevin McConnell
|
564a0f48ae
|
New Rails app
|
2024-06-21 13:19:56 +01:00 |
|