Closed stuartcusackie closed 9 months ago
I have increased all jobs to 120 seconds and still it fails:
I have now increased jobs to 300 seconds and it still looks like it is going to fail.
We're experiencing comparable issues, hope it can be addressed! 🙏🏼
@stuartcusackie @rubzie, some pretty big performance improvements coming in the next release https://github.com/statamic/seo-pro/pull/304 and https://github.com/statamic/seo-pro/pull/307, with more improvements yet to come...
My reports won't complete on a site with 400 entries
For example, I'm now generating a report for 1000 entries, without a queue even set up, in ~8.5 seconds...
@stuartcusackie @rubzie, some pretty big performance improvements coming in the next release #304 and #307, with more improvements yet to come...
Wooohoo nice, looking forward to it, thanks a lot @jesseleite! Then onto the next challenge, making SEO Pro work for multi site ;)
Will close this when we tag next version, but see https://github.com/statamic/seo-pro/pull/310 🏎️
Tagged 5.4.0 🤘
My reports won't complete on a site with 400 entries. I am using the Redis queue with Horizon at the default of 60 second timeouts:
I think ideally these jobs should be split (one entry per job). A job that takes 10 minutes to run seems like a bad idea, and this site isn't really that big compared to some.
If that's not happening then a simpler improvement would be a customisable queue in the config. At the moment the only option is to massively increase the timeout of all jobs on the default queue, which I don't like doing.
Thanks!