Problem: After refactoring the export to workers, triggering an export in the portal needs always 5 seconds. I expected a <1 seconds runtime for this call, since it starts only workers.

Reason:
When a worker queue call also starts the queue and the first worker, the triggerUrl call waits always 5 seconds for possible results, before it returns to normal processing. This 5 seconds are the delay, discovered above.

Currently this is no problem, since no User Action is directly affected. Export in Translate5 waits anyway until the export file is created and ready for download.
The severity of this issue increases when other API calls has to wait for the 5 seconds and / or Users are directly affected and has to wait the 5 seconds.
This could be the case in near future when making the export RESTful (one request for start the export, another one to get the results).