You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
EnvironmentApplication Name: StatamicLaravel Version: 11.34.2PHP Version: 8.2.26Composer Version: 2.8.2Environment: localDebug Mode: ENABLEDURL: localhostMaintenance Mode: OFFTimezone: UTCLocale: enCacheConfig: NOT CACHEDEvents: NOT CACHEDRoutes: NOT CACHEDViews: NOT CACHEDDriversBroadcasting: logCache: fileDatabase: sqliteLogs: stack / singleMail: logQueue: syncSession: fileStatamicAddons: 0Sites: 1Stache Watcher: Enabled (auto)Static Caching: DisabledVersion: 5.41.0 Solo
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered:
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 #11116It appears that the
->resetBlueprintCache()
being called withinStatamic\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
):After (
v5.38.0
):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
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: