NOTE:: Before reporting an issue, make sure you are running the latest version, currently 3.3.1
|Anonymous | Login | Signup for a new account||26-03-17 06:29 BST|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0017354||phplist application||Batch Processing||public||05-09-14 11:43||08-07-15 11:49|
|Target Version||next minor||Fixed in Version||3.2.0|
|Summary||0017354: Processing queue with multiple Messages sends messages sequentially.|
|Description||If you process a queue with 2 messages they will be send one after the other, almost in a sequential manner. In the 2.x.y version the sending of the 2 messages is interleaved. |
In my opinion the interleaving in V2 is a much better strategy the the one implemented in V3.
In the log we have these kinds of entries:
14 messages sent in 10.22 seconds (4930 msgs/hr)
Processed 0 out of 18437 subscribers
Processed 14 out of 16724 subscribers
Where most of the log entries have 0 sent in the most recently unenbargoed message.
|Steps To Reproduce||Process a queue with 2 messages to be sent. look at the webpage if process the queue manually to see clearly the log.|
|Additional Information||If you have a time limited configured queue (for instance 900 msgs/hour).|
For each attempt to send it will send mostly the message with the oldest embargo date, and if it can't send all the emails the remaining will the send mails to the second messages.
|Tags||Big Hitter phpList 3.1, Configuration and sending|
so, what do you propose ? What should happen?
I think 2.X did the same thing as 3.X except that 3.X fixed some bugs in counters, and therefore is more accurate in reporting what is actually going on. (Not entirely sure though).
|I propose that on each attempt to send emails the scheduler should split the avaialble emails between the messages. For instance if in the last hour you sent 800 msgs and you can send 900/hour. In this attempt you should try to send 50 emails of each message.|
That's a feature request. I can see why you want it, but that's very specific. Basically from most points of view, you'd want to send all as soon as possible. So, sending all of campaign 1 and then 2 is fine. However, in some cases, when you have two campaigns, you may want them to go out equally. But maybe others will want to have 2 only go out once 1 has been sent, etc. There are many options there.
|I think that the sequential effect can be acheived with embargo dates. The parallel on the other hand can't. And if you are sure that the behaviour did not change from 2.x, than it is a feature request. Your extension of my description hints at attribuiting weightes/ priorities at Messages / Mailing List :).|
|Copyright © 2000 - 2017 MantisBT Team|