Bug description
On our v5 site, deploys took 2 mins:
In v6, with the same content, they now can't deploy because the stache warming still takes > 10, even after I apply: #14816. Locally that PR decreases the stache warming from ~7:30 down to ~5:15.
On the v5 server we have the php cli memory set to 512M but on v6 we get out of memories until we set it 2G
I don't know why it's slower on the server (a big beefy EC2 instance) than my Mac.
Any help/advice would be appreciated.
Note I'm already excluding revisions and assets from the stache warming:
How to reproduce
Try to deploy our site on Forge.
Logs
Environment
Environment
Laravel Version: 13.16.1
PHP Version: 8.5.7
Composer Version: 2.10.1
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: NOT CACHED
Drivers
Broadcasting: null
Cache: redis
Database: mysql
Logs: stack / daily
Mail: smtp
Queue: sync
Session: file
Storage
public/storage: LINKED
Livewire
Livewire: v4.3.1
Statamic
Addons: 13
License Key: Not set
Sites: 4 (zakat.org (EN), zakat.org (AR), zakat.org (TR), Mobile App)
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.21.0 PRO
Statamic Addons
aryehraber/statamic-captcha: 1.17.0
jacksleight/statamic-bard-mutator: 3.0.5
jacksleight/statamic-distill: 1.2.0
marcorieser/statamic-livewire: 5.3.1
statamic-rad-pack/runway: 9.5.0
statamic-rad-pack/typesense: 3.2.0
statamic/seo-pro: 7.11.0
transformstudios/events: 6.1.1
transformstudios/front: 3.1.2
transformstudios/metal-prices: dev-prime
transformstudios/neon: dev-prime
transformstudios/prime: dev-fix/revisions-back-in-content
transformstudios/review: 6.0.0
Installation
Fresh statamic/statamic site via CLI
Additional details
Deployment script:
cd /home/forge/staging.zakat.org
git reset --hard HEAD && git clean -df
git pull origin $FORGE_SITE_BRANCH
$FORGE_COMPOSER install --no-interaction --optimize-autoloader --no-dev
# Prevent concurrent php-fpm reloads...
touch /tmp/fpmlock 2>/dev/null || true
( flock -w 10 9 || exit 1
echo 'Reloading PHP FPM...'; sudo -S service $FORGE_PHP_FPM reload ) 9</tmp/fpmlock
npm ci || npm install
npm run build
npm run cp:build
$FORGE_PHP artisan migrate --force
$FORGE_PHP please static:clear
$FORGE_PHP artisan optimize:clear
$FORGE_PHP please stache:refresh --exclude=revisions,assets
#$FORGE_PHP artisan queue:restart
Bug description
On our v5 site, deploys took 2 mins:
In v6, with the same content, they now can't deploy because the stache warming still takes > 10, even after I apply: #14816. Locally that PR decreases the stache warming from ~7:30 down to ~5:15.
On the v5 server we have the php cli memory set to 512M but on v6 we get out of memories until we set it 2G
I don't know why it's slower on the server (a big beefy EC2 instance) than my Mac.
Any help/advice would be appreciated.
Note I'm already excluding revisions and assets from the stache warming:
How to reproduce
Try to deploy our site on Forge.
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
Deployment script: