Performances issues when Filament goes in production
Hello,
I have an API that does real time on a specific domain. On this laravel application I've added filament on another specific domain to be able to monitor events. For the moment, the filament panel is empty, there's nothing in it, just a blank page.
It worked fine, but when I put it into production I noticed a 250% increase in memory, -50% requests per instance. We process around 5-6k req/s usually.
I suspect that the service provider is being called for each request even though it has nothing to do with it as the filament.x.com domain is not being called.
Do you have any ideas? Do you think it's possible that the service provider is doing greedy calculations every time laravel calls its service providers even though I've specified that the domain isn't concerned?
What are your recommendations ?
I have an API that does real time on a specific domain. On this laravel application I've added filament on another specific domain to be able to monitor events. For the moment, the filament panel is empty, there's nothing in it, just a blank page.
It worked fine, but when I put it into production I noticed a 250% increase in memory, -50% requests per instance. We process around 5-6k req/s usually.
I suspect that the service provider is being called for each request even though it has nothing to do with it as the filament.x.com domain is not being called.
Do you have any ideas? Do you think it's possible that the service provider is doing greedy calculations every time laravel calls its service providers even though I've specified that the domain isn't concerned?
What are your recommendations ?
