[E] Upgrades and Entity Maintenance Improvements#204
Merged
Conversation
Contributor
scryptmouse
commented
Mar 18, 2026
scryptmouse
commented
- Update to Ruby 3.4.9, Rails 8.1
- Use PG 18 client
- Significantly refactor entity maintenance for performance improvements
- Use eager loading in lieu of graphql-batch
- Merge in release branch and service tagging of docker images for Kamal deploys
* Use Valkey 8 images instead of Redis in docker compose, since that's what we're running when deployed * Use pgautoupgrade image for future upgrade tasks
The batch loaders seem to introduce unusable delay on very large dependency trees, like we see with layouts and templates, as well as entities in general. This uses a new approach to eager load things that are commonly fetched for entities and other mdoels, with special handling when invoking the layout itself.
* Remove ActiveSupport::Configurable (gone in 8.2) * Update rubocop & related lints
* Centralize all lifecycle entity maintenance into a single operation: `Entities::Maintainer`. This allows us better control over what happens when an entity is saved, avoid double-maintenance when Shrine persists attachments, etc. * Move entity indexing to an asynchronous operation * Improve schema properties application * Improve ordering refreshes to not rely on dry-effects, remove deprecated "deferred" logic * Move more upsert / delete operations to use merge instead * Make writing schematic texts significantly more efficient, merge all at once instead of n+1 and only update them if there are actual changes * Significantly improve performance of both calculating and auditing AuthorizedEntity, latter now runs in a second or two instead of 40+s
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.