rails-minify 0.3.0 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c682f7b5f509613697d35d78e163167b825525a03aae99fecb6ab430550f2429
-  data.tar.gz: dd258711680a2472583815a96af871f418d8fac5cf06f323c2dc7f102908e962
+  metadata.gz: 0723afe45486f260e81aee94e48c979e29a863991b960203a55397c932871792
+  data.tar.gz: 3bfa12203cc106068fbb22c6d844eff0ed68f564886a74be94953f1e817bebe1
 SHA512:
-  metadata.gz: 29a12e198162b3bd148f39d2f7be79e69aa32d471164120d1055a8c2960a97f7afee2a1dd2728b30dfe6e8f2d8f22b528a854420600f3ae1d3e325077265ce60
-  data.tar.gz: c2031ba5b96903be93f11d324afe736b18c476f420467e1a48503b4ac397ee24540812e7173819aa1ff6fd97e5025c7ac865616f7ad15d0db0498de29f2144eb
+  metadata.gz: e000f5a93f901772654e1c4219ea36a171970de119b6f2ada233a614bf198deb66c6e79334016dba7a7be17338d4532dbce711ad2d4538e1f22172e129327767
+  data.tar.gz: '09466303155a247edecff33e03b9b1fc5569abce784b9e95b3f471990b34a56c6ed1e6bd8f5affc8b5bb8030528398dc1e00a97c187932932f3f3092c2545a7e'

data/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.4.0 (2026-11-05)
+
+- Requires activerecord-minimizer 0.3.
+- Removed `config.rails_minify.enabled` and `config.rails_minify.zjit`. ZJIT after boot is in Rails main as `config.zjit = true` (rails/rails#59183); with enums gone too (activerecord-minimizer removed them: no measured gain in production, and they no longer worked on Rails main), `enabled` only turned on strict mode, so set `config.ar_minimizer.slim = true` instead. Setting either removed option prints a warning saying what to set.
+- `minify:doctor` suggests Rails' `config.zjit = true` for a ZJIT turned on before boot.
+
 ## 0.3.0 (2026-11-04)
 
 - `config.rails_minify.sql_profile = 0.01` samples requests and logs each distinct query and call site with its calls, time and rows, plus the request's SQL and instantiation time; `bin/rails minify:sql:report LOG=...` ranks actions and queries by total time, and with `EXPLAIN=1` adds SQLite query plans and flags full table scans and sorts without an index.

data/README.md

@@ -1,37 +1,20 @@
 # rails-minify
 
-Fewer generated Active Record methods, ZJIT turned on after boot, and checks
-for callback problems.
+Fewer generated Active Record methods, production profiling and
+configuration checks, and checks for callback problems.
 
 ```ruby
 # Gemfile
 gem "rails-minify"
 
-# config/environments/production.rb
-config.rails_minify.enabled = true
+# config/application.rb
+config.ar_minimizer.slim = true # strict mode
 ```
 
-`enabled` turns on what held up in production on a real app:
-
-* strict mode (`config.ar_minimizer.slim`): only readers and writers per column;
-* enum predicates and bang methods as plain methods (`config.ar_minimizer.enums`);
-* ZJIT after boot (`config.rails_minify.zjit`), in production on Ruby 4.1+.
-
-Each can still be set on its own (`config.ar_minimizer.enums = false`).
-Everything else is [experimental](#experimental) and off unless you set it.
-Ruby 3.4+, Rails 8.0, 8.1 and main.
-
-Turn it on in tests too, so a call to a method strict mode removed fails in CI
-rather than in production. In development, strict mode alone is enough: the
-same errors show up while you work.
-
-```ruby
-# config/environments/test.rb
-config.rails_minify.enabled = true
-
-# config/environments/development.rb
-config.ar_minimizer.slim = true # strict mode, without the rest
-```
+Set strict mode in every environment, so a call to a method it removed fails
+while you work and in CI rather than in production. Everything else is
+[experimental](#experimental) and off unless you set it. Ruby 3.4+, Rails 8.0,
+8.1 and main.
 
 ## Strict mode
 
@@ -54,20 +37,16 @@ instead, generated the first time each is called.
 
 ## ZJIT after boot
 
-```ruby
-config.rails_minify.zjit = true # instead of RUBY_ZJIT_ENABLE=1 / --zjit
-```
-
-`enabled` sets it in production on Ruby 4.1 and later; on 4.0, ZJIT isn't
-meant for production yet, so set it yourself if you want it there. ZJIT
-options still go in `RUBYOPT`, after `--zjit-disable` so they don't turn it
-on at startup: `RUBYOPT="--zjit-disable --zjit-call-threshold=2"`.
-
-`RUBY_ZJIT_ENABLE=1` turns ZJIT on before anything loads, so it also compiles
-what runs only while booting: RubyGems, requiring and eager loading, and the
-minimizers' own compiling. Rails turns YJIT on after boot (`config.yjit`) for
-this reason, but has no such setting for ZJIT; this is that one. It works on
-its own, without the rest of rails-minify.
+Rails main has this now: `config.zjit = true`
+([rails/rails#59183](https://github.com/rails/rails/pull/59183)), the ZJIT
+counterpart of `config.yjit`, so rails-minify no longer has its own setting.
+Use it instead of `RUBY_ZJIT_ENABLE=1` or `--zjit`, which turn ZJIT on before
+anything loads, so it also compiles what runs only while booting: RubyGems,
+requiring and eager loading. ZJIT options still go in `RUBYOPT`, after
+`--zjit-disable` so they don't turn it on at startup:
+`RUBYOPT="--zjit-disable --zjit-call-threshold=2"`. Use Ruby 4.1 or later;
+4.0's ZJIT isn't meant for production. `minify:doctor` reports a JIT turned on
+before boot.
 
 On Japan Voyage, per process after the same 132 pages: 12,612 → 9,557
 compiled methods, JIT code 45.9 → 35.3 MB, ZJIT memory 82.9 → 64.6 MB,
@@ -208,8 +187,8 @@ without it, under the same traffic (about 5,000 requests per half):
 
 | part | in production | in 0.2.0 |
 |---|---|---|
-| ZJIT after boot | HTML p50/p90/p99 75/131/231 → 70/126/208 ms, ~25 MB less per worker (an hour before against an hour after) | on with `enabled` (production, Ruby 4.1+) |
-| enums | the same medians; that hour's lower mean and p99 came from a few slow requests, as it changes no allocations on these pages | on with `enabled`: harmless, no measured gain |
+| ZJIT after boot | HTML p50/p90/p99 75/131/231 → 70/126/208 ms, ~25 MB less per worker (an hour before against an hour after) | on with `enabled` (production, Ruby 4.1+); now Rails' `config.zjit` |
+| enums | the same medians; that hour's lower mean and p99 came from a few slow requests, as it changes no allocations on these pages | on with `enabled`; removed since (no measured gain, and it broke on Rails main) |
 | strict | the same latency and memory; no calls to a removed method | on with `enabled`, so production runs what the tests run |
 | small records | no difference (tens of records per request) | experimental |
 | route helpers | no difference in view time | experimental |
@@ -219,8 +198,8 @@ without it, under the same traffic (about 5,000 requests per half):
 | callbacks | no faster, ~20 MB more per worker | experimental |
 | patches | no difference (view time 25.3 vs 26.8 ms) | experimental |
 
-ZJIT after boot is the one part with a clear effect. What `enabled` turns on
-is what Japan Voyage runs.
+ZJIT after boot is the one part with a clear effect, and it is in Rails now.
+Japan Voyage runs strict mode and Rails' `config.zjit`.
 
 What the benchmarks speed up is per call: a method call, a Hash, a helper.
 A page there spends ~30 ms in Active Record and ~30 ms in views, and those

data/lib/rails_minify/doctor.rb

@@ -75,7 +75,7 @@ module RailsMinify
 
       Finding.new(:jit_before_boot, "JIT turned on before boot: #{found.join(", ")}", WHY_BOOT,
         "drop it and turn the JIT on after boot: config.yjit = true for YJIT, " \
-        "config.rails_minify.zjit = true for ZJIT.")
+        "config.zjit = true for ZJIT (Rails main).")
     end
 
     def jit_options

data/lib/rails_minify/railtie.rb

@@ -8,7 +8,7 @@ module RailsMinify
     # minimizers' options.
     config.before_initialize do |app|
       Railtie.apply_ab(app.config)
-      Railtie.apply_enabled(app.config)
+      Railtie.warn_removed(app.config)
     end
 
     # In an A/B run (rails-minify-ab), group B gets config.rails_minify.ab
@@ -23,20 +23,16 @@ module RailsMinify
       config.log_tags = [*tags, AB.log_tag(group)]
     end
 
-    # `enabled` turns on what made no page slower in production and is worth
-    # having for its own sake: strict mode (fewer generated methods, production
-    # runs what the tests run), enums and ZJIT after boot. Everything else stays
-    # off unless set on its own. ZJIT, like Rails' config.yjit default, not in
-    # development and test, and only from Ruby 4.1: 4.0's ZJIT isn't meant for
-    # production yet.
-    def self.apply_enabled(config, env: Rails.env, ruby: RUBY_VERSION)
-      options = config.rails_minify
-      return unless options.enabled
-
-      ar = config.ar_minimizer
-      ar.slim = true if ar.slim.nil?
-      ar.enums = true if ar.enums.nil?
-      options.zjit = !env.local? && Gem::Version.new(ruby) >= Gem::Version.new("4.1") if options.zjit.nil?
+    REMOVED = {
+      enabled: "set config.ar_minimizer.slim = true for strict mode, and Rails' config.zjit = true for ZJIT",
+      zjit: "use Rails' config.zjit = true (Rails main), which turns ZJIT on after boot the same way",
+    }.freeze
+
+    # Options earlier versions read; setting one now would quietly do nothing.
+    def self.warn_removed(config, out: $stderr)
+      REMOVED.each do |name, instead|
+        out.puts "rails-minify: config.rails_minify.#{name} was removed; #{instead}." unless config.rails_minify[name].nil?
+      end
     end
 
     PATCHES = {
@@ -72,18 +68,6 @@ module RailsMinify
       SqlProfile.install!(rate: rate) if rate
     end
 
-    # ZJIT from after boot, as Rails does for YJIT (config.yjit): the code
-    # that only runs while booting (requiring, eager loading, the minimizers'
-    # compiling) isn't compiled. Japan Voyage, per process: 24% fewer
-    # compiled methods, 18 MB less JIT memory, the same speed.
-    initializer "rails_minify.zjit" do |app|
-      config.after_initialize do
-        next unless app.config.rails_minify.zjit && defined?(RubyVM::ZJIT.enable) && !RubyVM::ZJIT.enabled?
-
-        RubyVM::ZJIT.enable
-      end
-    end
-
     rake_tasks do
       namespace :minify do
         prepare = lambda do

data/lib/rails_minify/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RailsMinify
-  VERSION = "0.3.0"
+  VERSION = "0.4.0"
 end

data/lib/rails_minify.rb

@@ -9,15 +9,11 @@ rescue LoadError => e
   raise unless e.path == "ap_minimizer"
 end
 
-# One switch:
+# Strict mode, in every environment, so a call to a removed method fails in CI:
 #
-#   # config/environments/production.rb
-#   config.rails_minify.enabled = true
+#   config.ar_minimizer.slim = true   # only readers and writers per column
 #
-# turns on, unless set otherwise on their own:
-#   config.ar_minimizer.slim   strict mode: only readers and writers per column
-#   config.ar_minimizer.enums  enum predicates/bang methods as plain methods
-#   config.rails_minify.zjit   ZJIT after boot
+# ZJIT after boot is Rails' own config.zjit (Rails main).
 #
 # Experimental, each off unless set: the other minimizer options
 # (ar_minimizer.views, .load_time, .small_records, as_minimizer.unroll_callbacks,

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rails-minify
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.4.0
 platform: ruby
 authors:
 - Sampo Kuokkanen
@@ -15,14 +15,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.2'
+        version: '0.3'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.2'
+        version: '0.3'
 - !ruby/object:Gem::Dependency
   name: activesupport-minimizer
   requirement: !ruby/object:Gem::Requirement
@@ -37,10 +37,10 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.2'
-description: 'One switch for what held up in production: Active Record strict mode
-  (only readers and writers per column), enum methods without closures and ZJIT turned
-  on after boot. minify:check finds callback problems. Experimental: patches for parts
-  of Rails and common gems that redo work on every request, and the other minimizer
+description: 'Active Record strict mode (only readers and writers per column), minify:check
+  for callback problems, minify:doctor for production configuration that costs speed
+  or memory, and SQL profiling from production traffic. Experimental: patches for
+  parts of Rails and common gems that redo work on every request, and the other minimizer
   parts.'
 executables:
 - rails-minify-ab
@@ -86,6 +86,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 4.0.20
 specification_version: 4
-summary: Strict Active Record attribute methods, ZJIT after boot, and checks for callback
-  problems
+summary: Strict Active Record attribute methods, production profiling, and checks
+  for callback problems
 test_files: []