#V4 much slower than V3
25 messages · Page 1 of 1 (latest)
Not expected at all. v4 should be faster than v3. Is this the only Page where v4 is slower? Or does this happen to all pages?
I'm assuming the results are consistent and it's not a one off? As Dennis said, you need to do a comparison across the app and see if this is common or if it only happens on that page
Either way, a sample of one is not enough. And I can see there are some differences in the pages (eg the number of queries) so you'd need to see what causes the slowdown
I've the best times from V3 (loading: 2.7s) and V4 (loading: 4.4s).
So I guess they tried multiple runs
I can also see, that the used memory multiplied by 3 and that you migrated from L10 to L12.
Video from V3: https://imgur.com/a/x19i4mO V4 Video here : https://imgur.com/a/GtZdvm7 (numbers on top left are the execution time of \App\Filament\Resources\EventPatientReports\Schemas\EventPatientReportForm::configure method)
(please note the page is refreshed a few times, but there are no reload indicators on screen).
Since the slow loading is not from the method, I don't know what the issue might be,
Again:
- Is this the only Page where v4 is slower?
- Does this happen to all pages?
is only on this. Others have +/- the same performance. But they are very simple Forms/Tables.
- Do you have OpCache enable?
- Can you try running
artisan filament:optimzie? - Do you have similar results on a different machine? Maybe Hosting?
Can you share that Form?
You could also check this section: https://filamentphp.com/docs/4.x/introduction/optimizing-local-development
Didn't know we had this. Thanks for sharing.
It is a "new" section 😅
I need to save this to my snippets 😅
me too 😅
Debugging in Laravel Herd can significantly slow down your app 😵
I tried it
Great I only have the free version. One thing less to worry about 😅
I have opcache enable and running. the same with optimize command. Domains share the same settings. I disabled the debug bar, and the difference in loading time remains: https://imgur.com/a/0h0zDvD The form Is built dynamically from DB information.
In V3, we don't see theses 'jumps' in the timeline when rendering view, even though there are many more view to render.
That probably means something else is loading.
Sounds like the data isn't fetched at once, but some components fetch data again 🤔
Do you haveany $get() in this form?
No. I do not any any injection on any element. I can share the form code, but it's generated from a DB...
I’m sure I’m wrong but I would start with those 80+ db queries. That seems insane to me.