PushTranslation flow comparison between 11.0.0 and 12.0.0
A schematic depiction of a PushTranslation flow shows how the new background tasks system improves the PushTranslation throughput.
Former flow
In the 11.0.0 version of the Background Task System, when the Client sent one publication for translation, only one task, the first one, was created for this publication, and the process passed around an event data containing the data for all remaining objects. Any valid Background Task Service could then pick up this single task. If there was more than one Background Task Service active, only one could take on this event.
When the Background Task Service had finished executing this task, the next task was created for this publication, from the event data containing X-1 remaining objects, and could then be picked up. And so on, passing around an event that contained all remaining objects and that was getting smaller and smaller. In this flow, one publication could be processed by one Background Task Service at the same time. A scaling would have no effect on the PushTranslation speed.
Current flow
In the 12.0.0 version of the Background Task System, when the Client sends one publication for translation, all the tasks for this publication are created from the start. If several valid Background Task Services are active at that time, each of them can pick up a task. This enables a certain degree of parallel processing for a given publication at a given time.