Open
Description
Bug description
Stache warming is up to 10x slower since the v5.38.0
release and we were able to determine that this PR was the cause #11116
It appears that the ->resetBlueprintCache()
being called within Statamic\Fields\Blueprint::setParent(...)
is the main culprit.
This issue also extends to everywhere on our site, it's not just limited to warming the stache.
Before (v5.37.0
):
$ php artisan cache:clear && time php artisan statamic:stache:warm
INFO Application cache cleared successfully.
INFO You have poured oil over the Stache and polished it until it shines. It is warm and ready.
real 0m6.934s
user 0m6.041s
sys 0m0.590s
After (v5.38.0
):
$ php artisan cache:clear && time php artisan statamic:stache:warm
INFO Application cache cleared successfully.
INFO You have poured oil over the Stache and polished it until it shines. It is warm and ready.
real 0m45.086s
user 0m42.860s
sys 0m1.469s
How to reproduce
Create lots of content with different blueprints that contain many fields and run php artisan cache:clear && time php artisan statamic:stache:warm
.
Logs
No response
Environment
Environment
Application Name: Statamic
Laravel Version: 11.34.2
PHP Version: 8.2.26
Composer Version: 2.8.2
Environment: local
Debug Mode: ENABLED
URL: localhost
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: NOT CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Statamic
Addons: 0
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 5.41.0 Solo
Installation
Fresh statamic/statamic site via CLI
Additional details
No response