Ruby on Rails: STI Speedup, Variant Flexibility and Schema Fix

Single-table inheritance gets a merged performance fix to avoid building descendant lists per record, while Active Storage and schema-cache changes restore flexibility and reliability. Deployment tuning guidance rounds out a day focused on lower production overhead.

Duration: PT2M26S

Episode overview

This episode is a short developer briefing from Ruby on Rails.

It explains recent repository work in plain language.

  • Show: Ruby on Rails
  • Published: 2026-09-21T13:15:00Z
  • Audio duration: PT2M26S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's Monday, September 21st, 2026.

The clearest signal today is cutting hidden per-record costs, with one merged performance fix leading a set of reliability and flexibility corrections.

First, single-table inheritance gets leaner. In pull request 58783, merged as commit 929d092, Rails stops building the full descendant list just to verify a resolved subclass. Previously, every instantiated record walked the class tree, allocating intermediate arrays and then scanning the result, so cost multiplied…

Second, restoring control you may have lost in recent upgrades. Pull request 58835 revisits variant processing in Active Storage. The newer process setting offered three static modes and is set to replace the preprocessed setting in Rails 9, but preprocessed could accept a symbol or procedure evaluated per record.…

Separately, pull request 58833 updates the tuning performance for deployment guidance, a sign to review production settings alongside code changes. Even without full details in the summary, the focus on deployment tuning aligns with the inheritance work: lower framework overhead in production.

What's next: if you use cached schemas or conditional variants, test…

Nearby episodes from Ruby on Rails

  1. Weekly Recap - Query Correctness, Faster Boot, and Ractor Safety
  2. Upstream Compatibility and Schema Load Fixes
  3. Concurrency Bugs and Test Hygiene
  4. Association Scopes Get an Honesty Check
  5. Quietly Fixing Data Correctness Bugs
  6. Performance Cleanup Across the Stack
  7. Quiet Correctness Fixes and Ractor Readiness
  8. Locking Down the Edges