You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2020. It is now read-only.
The GUI will register each started job with DocJobUpdater which then updates each job regularly with a single request.
Especially when large batches of jobs are started this results in the GUI sending 20-30 GET requests per second to the server.
Today at noon, the server has handled 200.000 GET requests regarding job updates (total is 260.000, or 220.000 GET requests)
It would be much easier on the server if the GUI could just query for the jobs with state=RUNNING or state=UNFINISHED and query those specifically that were include, but are missing in that list at some point, in order to check the outcome.
The text was updated successfully, but these errors were encountered:
The GUI will register each started job with DocJobUpdater which then updates each job regularly with a single request.
Especially when large batches of jobs are started this results in the GUI sending 20-30 GET requests per second to the server.
Today at noon, the server has handled 200.000 GET requests regarding job updates (total is 260.000, or 220.000 GET requests)
It would be much easier on the server if the GUI could just query for the jobs with state=RUNNING or state=UNFINISHED and query those specifically that were include, but are missing in that list at some point, in order to check the outcome.
The text was updated successfully, but these errors were encountered: