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
I see currently the listJobs method gets the list of jobs and process them sequentially in a for loop. Is it possible to make it parallelized by using threads? so faster responses can be had at the rest client.
Also, I see when I use /job/detail/, the corresponding method iterates over the list of running jobs until the job id is matched and the details of the job are fetched -- this kind of slows down the operations for client sometimes, it is perhaps okay to just get the jobstatus of given job id and then get the details if the jobid is genuine?
thanks.
The text was updated successfully, but these errors were encountered:
Hi @ryukobayashi
I see currently the listJobs method gets the list of jobs and process them sequentially in a for loop. Is it possible to make it parallelized by using threads? so faster responses can be had at the rest client.
Also, I see when I use /job/detail/, the corresponding method iterates over the list of running jobs until the job id is matched and the details of the job are fetched -- this kind of slows down the operations for client sometimes, it is perhaps okay to just get the jobstatus of given job id and then get the details if the jobid is genuine?
thanks.
The text was updated successfully, but these errors were encountered: