Performance question
Hey guys,
I'm evaluating Filament as an admin panel solution. I launched the demo locally using Docker with a Laravel Octane server. Everything works fine, except for one issue: performance when loading tables with 50 or more records. For example, fetching 50 records (orders, customers, etc.) takes over 1 second, even locally, with Laravel Octane and the latest PostgreSQL.
I've applied all the optimizations listed on the "Installation" page. Is this performance typical for Filament, or is the demo just not optimized? The hosted demo app behaves the same way.
6 Replies
This is Filament's pitfall, we would encourage searching and filters. Thought v4 does have signifact performance improvements (200%). But essentially it's the re-rendering of the html and sending it over the wire it adds overhead.
I see, thank you for clarifying. When is v4 planned to be launched?
found it, June 10, 2025
did you also enable pwa mode?
PWA isn't really advised tbh. There tends to be more bugs than problems it solves.
Just saying 'takes over 1 second' doesn't make much sense when talking about performance. What's the brakedown of the request? What's the expected performance?
In any case, we've been using Filament in production for years (no Octane yet but we're working on it) and it's fine.
If you're evaluating it I'd say there are a few performance 'issues'
1) Filament has a *lot *of 'gotchas' that you need to be careful of. Because it's so easy to use, you might not think of the side effects of the code you write. Even some examples from the docs might lead to crazy results in production if not careful
2) Modals are not 'real' modals - I'm not 100% sure how it works, but when you load a modal on a table, it kinda also reloads the table. I think this is going to be fixed in v4 but I'm not sure. (FWIW this is a Livewire issue)
All in all, we didn't run to many performance issues that are unique to Filament - slow queries are going to be slow no matter the framework. But if you're just starting to use it, you will run into problems until you figure out its quirks.
My personal opinion is that the admin panel doesn't need to be hyper-optimised (how many people are going to be accessing it?) but that's just me ¯\_(ツ)_/¯
I dont know, I'm using it for a year now and have a lot better performance, and no bugs so far