Over the years, the Filament team has done a lot of work behind the scenes to make Filament the fastest, most performant option available for building your applications in the TALL stack. Most recently, they did a huge rework of the tables package that massively decreased render time in the v3 to v4 upgrade.<\/p>\n
Well, over the past few months, they’ve been back at it again trying to squeeze some more performance out of Filament. This time, they’ve made a bunch of adjustments across the entire first-party Filament package ecosystem, and are excited about the preliminary performance gains they are seeing in their testing!<\/p>\n
However, before the team launches a release this big to all Filament applications everywhere, they want to make sure that they give these changes time to be used in real-world applications. To do this, the team is launching all of these changes with a new beta version of both Filament v4 and v5 that you can install into your Filament applications today! All they ask is that you keep them up to date with any issues you bump into locally as well as giving them feedback into how much of a performance improvement you see in your specific use case.<\/p>\n
#<\/a>Installation instructions<\/p>\n You can get up and running with either the v4 or v5 beta in just a few simple steps:<\/p>\n Update your composer.json constraints for any open source filament\/* package to either ^4.12@beta or ^5.7@beta depending on which major version of Filament you are currently running Just like that, without any major code changes, you should be up and running with a more performant version of Filament.<\/p>\n As always, this is the part where I add my usual disclaimer about not using these beta versions in production. They are, by nature, potentially unstable, so be cautious as to where you use these beta versions! However, they are perfectly fine to run locally or in a staging environment.<\/p>\n Please add a reply to this GitHub discussion<\/a> so we can get a gauge on how many people have tested the beta whether you experience issues with the beta or not. We need to know that it’s working well with no issues just as much as we need to know of any bugs!<\/p>\n #<\/a>What changed?<\/p>\n If you are curious as to what has changed to give Filament such a performance boost, here are a few of the stand-out adjustments that we’ve made across the ecosystem:<\/p>\n Forms & schemas<\/p>\n Significantly faster rendering of large forms, thanks to refactoring Blade views into simple HTML generation functions. Tables<\/p>\n Faster overall table rendering, including optimised rendering fast-paths for basic text columns and actions, alongside and various other internal memoizations. Panels & resources<\/p>\n Memoized model-to-resource lookups, resource slugs, resource page names, and relation manager visibility. Widgets & charts<\/p>\n Stat chart widgets no longer import the entire Chart.js library, reducing bundle size. Other<\/p>\n A more efficient ComponentAttributeBag that replaces Laravel’s.
\nRun composer update to pull the latest beta version
\n$$$<\/p>\n
\nRepeaters, builders, and repeatable entries now memoize their internal child schemas more aggressively.
\nComponent configuration, colours, descriptions, icons, and tooltips are now memoized.
\nSelects resolve their options fewer times while rendering in some situations.<\/p>\n
\nState formatting runs fewer times per cell in some cases.
\nOptimised table reordering for BelongsToMany relationships.
\nInternal parts of the query builder are now memoized rather than rebuilt repeatedly.<\/p>\n
\nFaster navigation group sorting.<\/p>\n
\nStat charts no longer redraw when the underlying data hasn’t changed.<\/p>\n
\nFixed a memory leak caused by action modal event listeners not being cleaned up.
\nFewer redundant config fetches and button component instantiations across requests.
\nMore efficient filesystem disk caching and file-existence checks.
\nNotification Alpine components now serialise less data.<\/p>\n