Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Make the batch size a global setting instead of a per-fetcher setting.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | batch_size-2804333-2.patch | 1.68 KB | ModernMantra |
| |||
| #4 | batch_size-2804333-4.patch | 4.68 KB | ModernMantra |
| |||
| #4 | batch_size-2804333-4-test_only.patch | 518 bytes | ModernMantra |
Comments
Comment #2
ModernMantra CreditAttribution: ModernMantra at MD Systems GmbH for MD Systems GmbH commentedComment #3
miro_dietikerThe changes are completely unrelated to the goal.
Making them a global setting means showing the form at admin/config/system/inmail
The selection should be REMOVED from the ImapFetcher. It should just consider the global setting.
The problem with this setting will be, it still doesn't scale without major unchanges. The resource consumption is multiplied with the fetcher instances. Let's first move it there and then reconsider the scaling.
Comment #4
ModernMantra CreditAttribution: ModernMantra at MD Systems GmbH for MD Systems GmbH commentedMade some progress, hope it is going in good direction... :) No interdiff since so far it was wrong way of doing the issue.
Comment #6
miro_dietikerCommitting with changing number from 100 to 20.
No upgrade path is still fine with current changes.
Creating follow-up: #2807545: Make inmail cron batch scaling