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.
Right now Feeds starts a batch job no matter whether the batch size per page load limit is reached or not. This could be easily modified so that we only batch if a job doesn't finish on the same page load.
Patch coming.
Comment | File | Size | Author |
---|---|---|---|
#2 | 727332-2_conditional_batching.patch | 1.32 KB | alex_b |
#1 | 727332-1_conditional_batching.patch | 2.44 KB | alex_b |
Comments
Comment #1
alex_b CreditAttribution: alex_b commentedTrivial patch - how does this behave on the ground? Users that batch heavy feeds may appreciate the batch starting right away and not only after a first page load. On the other hand, I really don't like much the batch bar popping up for very light and quick imports like RSS feeds + data module.
I'm still on the fence on this one.
Comment #2
alex_b CreditAttribution: alex_b commentedReroll after recent commit.
Comment #3
rjbrown99 CreditAttribution: rjbrown99 commentedI'm using this now, no problems here.
Comment #4
alex_b CreditAttribution: alex_b commentedI am going to postpone this for now. Using the batch API no matter whether either case seems to be work fine.
Comment #5
kenorb CreditAttribution: kenorb commentedHow about the option on import/% under 'Debug Options' to optionally parse without batch, as sometimes there is some needs for some debugging?
Comment #6
kenorb CreditAttribution: kenorb commentedTried to implement it in 2.x, but there are too many references to these options, so I won't have time to do that. Here is my initial attempt. Probably this can be done in different way.