Timeline for Drush and batch
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2014 at 19:33 | comment | added | greg_1_anderson | A bigger limitation than the max execution time for Drush script is memory exhaustion. It can be pretty easy to run out of memory, even with memory_limit=-1, if you do a really huge processing job. | |
| Aug 8, 2014 at 15:26 | comment | added | Mołot | @Nuctorn Strange, it worked for me from php.ini - or so I thought. Anyway, thanks for a pointer :) I agree that leaving it 0 may be bad for server's health. Scripts are not daemons that need to stay in background all the time. | |
| Aug 8, 2014 at 15:13 | comment | added | mgoubert | midwesternmac.com/blogs/jeff-geerling/… When running PHP from the command line the default setting is 0. I think it is not a good practice to leave it 0. Running php could slow down the server this way. | |
| Aug 8, 2014 at 14:54 | comment | added | Mołot | @Nuctorn Are you sure you set it in the correct php.ini? Also, batch operation means steps are sent to separate processes, so maybe one of them indeed died, and you just haven't noticed? I never bothered to investigate how Drupal's batch works internally. It worked. It allowed execution of "too long" jobs. That was all I needed to know. | |
| Aug 8, 2014 at 14:51 | comment | added | mgoubert | i placed max_execution_time on 16s. I did a 20s sleep in my batch operation. But it stil gets executed 'without' an timeout error. | |
| Aug 8, 2014 at 14:35 | vote | accept | mgoubert | ||
| Aug 8, 2014 at 14:22 | history | answered | Mołot | CC BY-SA 3.0 |