rails-minify 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bf98d2d12a8005e5ef2755cd6bba97a32122a7dd2514518e9a749d1ba367af00
-  data.tar.gz: 878a2fab37d90963eb4b4d5924d7b3437847672741471d84ea6cefc686cb7ca1
+  metadata.gz: 44f089252dbde289b9e5cfeb25c2613e91544e92a1235369ec7c4457992e477b
+  data.tar.gz: c768e54a78cd0ee553f8732f019dc4eab9fff3c5c72d4ef9d30d23abc68b2994
 SHA512:
-  metadata.gz: 2baf13ba8db10c35cfaccfaf86b6c966b11555b9b232c1710da044a37dad166f96dee80cdc2380db98321a845c612e80f3a3648dbc515b31f9402a54bc393599
-  data.tar.gz: b26a83ac5f86fc456c18444e7eba578cb095fa897ee4bac9a508a10047a9164fc8d22197dc0ae6f7f2c7193ca32a437fe1b8fc35c7c9ab873d9091c936be57a0
+  metadata.gz: da6b92c40d4f1fada0154fb362cd52c8a56e458b67e5d959e20084bb4e37f25a8be93d7d86bc065d6a71ac09dc4763c79fbada65a4f7a73c281c8b9fef511d1b
+  data.tar.gz: 8cca5d4c9850e66798cdb80127907dbfc64cdf5643d1064a7ce01be6bfdd8f46b79bbf63e9e8c80775dd6c3453d9877537bd6951707cb434378049fdb0a92227

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.1.3 (2026-10-18)
+
+- `config.rails_minify.zjit = true` turns ZJIT on after boot, as `config.yjit` does for YJIT, instead of `RUBY_ZJIT_ENABLE=1` compiling boot-only code too. Japan Voyage, per process: 24% fewer compiled methods, 18 MB less JIT memory, about 25 MB less RSS, the same speed.
+
 ## 0.1.2 (2026-10-18)
 
 - `minify:check` also fails on callback chains longer than `callback_limit` (default 5, `ApplicationController`'s callbacks excluded) and on model callbacks that save their own record again; `callback_limit_mode` and `callback_loops` set either to `:warn`. Works without the rest of rails-minify turned on; the manifest check runs only when there is a manifest.

data/README.md

@@ -84,6 +84,22 @@ For parts of Rails and common gems that redo work on every request.
   installed when OmniAuth already does this itself (it then has a public
   `Strategy#passthrough?`, as in the version proposed upstream).
 
+## ZJIT after boot
+
+```ruby
+config.rails_minify.zjit = true # instead of RUBY_ZJIT_ENABLE=1 / --zjit
+```
+
+`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.
+
+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,
+RSS about 25 MB less, the same CPU time per page.
+
 ## Numbers
 
 Japan Voyage, 132 production pages, with everything on (strict mode after

data/lib/rails_minify/railtie.rb

@@ -42,6 +42,18 @@ module RailsMinify
       end
     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.1.2"
+  VERSION = "0.1.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rails-minify
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - Sampo Kuokkanen