Replies: 1 comment 1 reply
-
I don't think that is possible, because the query size determines the amount of jobs that need to be processed. Perhaps for your use case it would be better to skip the internal queuing and wrap it in a job of your own? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First of all I would like to thank you and say what a wonderfull piece of software you have created.
I am trying to export over 200k records and it works amazing however, everytime I call my Exportable it loads for about 5-10 seconds because my querySize() is taking that long. I can not optimize it further.
Therefor I would be gratefull when there would be a possibility to make the querySize() happen the first time the job processing is called in the background.
This would allow me to return directly after calling: (new DataExport)->queue('public/exports/data.csv'); instead of waiting 5-10 seconds before returning.
Beta Was this translation helpful? Give feedback.
All reactions