Our application has several thousands of entries running in "split mode" where Collections are still file based, and we're experiencing significant slowdown when the UpdateCollectionEntryOrder job is running synchronously. As previously discussed in this issue, there's certainly some room for optimization and clarification when it comes to updating entry order as well as entry URIs. This is of course a challenging task, since I imagine it'd be hard to get around the fact that you need to update every entry in a collection to get the order right.
Nevertheless, a very helpful first small step to improve this would be the ability to control which queue connection is used for the job. Being forced to used the default queue connection does create problems for us with our current environment setup.
Our application has several thousands of entries running in "split mode" where Collections are still file based, and we're experiencing significant slowdown when the
UpdateCollectionEntryOrderjob is running synchronously. As previously discussed in this issue, there's certainly some room for optimization and clarification when it comes to updating entry order as well as entry URIs. This is of course a challenging task, since I imagine it'd be hard to get around the fact that you need to update every entry in a collection to get the order right.Nevertheless, a very helpful first small step to improve this would be the ability to control which queue connection is used for the job. Being forced to used the default queue connection does create problems for us with our current environment setup.
PR: https://github.com/statamic/eloquent-driver/pull/210