2

We've set up a task that's supposed to run through an external folder with images and resize them into 3 sizes each. This results in about 13000 tasks (one task per image). I thought each task was on a separate thread? But now the tasks are running for only 60 seconds (max_execution_time), then stopping. The task says running in the database, but it has just stopped, and the error log says max execution time was exceeded.

Is there a way around this? Would sub tasks change any behaviour?

2

Tasks are just another PHP request and they are subject to the same web server and php.ini limitations as a "normal" request.

Sounds like you just need to up your max_execution_time.

| improve this answer | |
  • But are all the tasks run as one request? Or are they split up into separate requests? Because each task takes less than a second to complete, but we're getting maxed out after 30 seconds of running tasks. It usually completes around 80-100 tasks before shutting down. – peirix Jun 26 '15 at 7:27
  • 1
    Yes - a task is run as one request even if it has multiple sub-tasks. – Brad Bell Jun 26 '15 at 17:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.