is this normal?
I just installed filament, I followed the documentation and I have the dashboard, I also added a crud of users, I have these loading times from 0.94 to 1.70 in the worst case
on the local machine it is similar, i run the local machine in windows,
I have nothing, it is as it is when following the steps in the documentation


35 Replies
What spec is your VPS
1gb ram, 2 vCPU use something basic to test
Well, something without filament has worked better for me, but I was thinking of going up to something with 8 GB RAM / 8 vCPU
in case of not being able to improve the time
Filament.com runs on the basic DO $5 VPS... So filament doesn't need huge resoruces, an NMVE is benefical
did you run php artisan optimize? Have you tried redis?
What times do you get when changing the section in the side menu?
Yeah. I have used most of the commands for cache, routes and that, I have not used redis
250ms uncached, 200ms cached
in our latest app in a 5$ DO droplet
rendering a table with 50 records with 7 columns.
The time difference is big, mmm, maybe it's a bad installation?
are you using the latest package versions?
use this command composer require filament/filament -w
If I specified the version it gave me an error
ntfs kinda sucks, have you tried redis by any chance? On windows you gotta have wsl and install redis-server there
yeah windows sucks on that because ^ is an escape operator and it messes with the install
what shows in the composer.json?
i add this line "filament/filament": "^3.2"
try to run composer update to see if anything changes
Some things were updated, but the situation is similar, maybe try to reinstall everything
what version of laravel do u recommend?
I'm running 11
11.0.0?
latest laravel 11 version
but I dont think the problem is in the laravel version tbh
anyway, thanks for the help
I get about 800-1000ms per page load with debugbar enabled
600-800ms per page change without debugbar enabled.
APP_DEBUG=false you just need to have this right?
Yeah to disable the debug bar as that has a lot of overhead of course since it's insepecting everything
And that's without any caching at all, using Herd for tech stack.
I get 834ms in dashboard, in the user crud panel 1.20 seconds its good?


For the shop/customers list I get 497ms load.
No that's not great, what DB are you serving from sqllite? If so and you are not using an NMVE that will have a bigger impact as it's heavy disk read/write
i use mysql
use that for the crud of users

Given it's 1 user... with a full cache refresh I get

With this I realize that something is wrong
It's jsut your tech stack I suspect, likely a poor one.
When using a VPS just use Ploi or laravel coud where the VPS is highly optimized by default
I'll do a reinstall, and try to get a better vps, otherwise I'll go traditional, thanks anyway
Icons cache?
in the end, install laravel herd and locally it was better, times from 0.60 to 0.80, better than before, thanks for the help

in server 0.76 in the max
Nice!
Yep, heard is highly optimised 🙂