How is demo.filamentphp.com deployed?
I was wondering how filamentphp deploys their demo site because it feels so fast when accessed. For comparison, I use aaPanel (nginx) on a VPS with 8GB RAM. It takes 3.09 seconds just to load the default dashboard page without dynamic widgets. While demo.filamentphp.com only takes 900ms to load the dashboard containing dynamic tables.
So, is the demo using a container or using a panel-based service like cPanel, Plesk, etc.?
Solution:Jump to solution
what is your deployment script?
check:
https://laravel.com/docs/11.x/deployment#main-content
https://filamentphp.com/docs/3.x/panels/installation#deploying-to-production...
5 Replies
I guess it's a small VPS managed through Forge?
3s sounds like you don't have OPCache turned on
Thanks for the answer. I have experimented with using containers in Docker as well as with PHP installed on the system via aaPanel. In both I have the OPCache extension enabled.
Docker + Nginx = 1.5s
aaPanel + Nginx = 3s
Still not as fast as demo.filament.com, but shows significant results.
Solution
what is your deployment script?
check:
https://laravel.com/docs/11.x/deployment#main-content
https://filamentphp.com/docs/3.x/panels/installation#deploying-to-production
Caching filament components and icons helps a lot. Just follow all the tips mentioned above. 👆
I've tried both ways, from
optimize:cache and creating a filament view cache, and the result is about 1 second. I'm okay with that, compared to 3 seconds before. It could be less than a second if the ping to my VPS is less than 200ms.