You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- We previously we doing some calculation based on `$numberOfProcesses` and `$numberOfProcessesDefined`. In reality those calculation were not related directly to those values, but about the fact that child processes we spawned. Indeed when they are not, i.e. we do the processing in the main process, then the segment size and the number of segment becomes irrelevant. I think the logging should be updated to reflect this and better document when child processes are spawned, but this is out of scope of this PR. To address the direct issue though, we now pass directly `bool $shouldSpawnChildProcesses`
- The calculation of the segment size and number of segments was incorrect, most likely due to some confusion as to when it is run in the main process or not.
- The total number of batches was incorrect:
- when no child processes are spawned, it is not the segment size that matters but the total number of items
- when child processes are spawned, it may be that the last process does not need to run its maximum number of batches if there is not enough items
0 commit comments