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
Is your feature request related to a problem? Please describe.
Yes, the current issue is the lack of visibility regarding the waiting time for a request to be processed using cdsapi. Users are unable to know how long they will have to wait for their request to be run.
I find it challenging and inefficient to work with the cdsapi when I'm unable to determine the length of time I'll need to wait for my request to be processed. This uncertainty makes it difficult to plan and manage data retrieval tasks effectively.
Describe the solution you'd like
I would like to see an enhancement in the cdsapi that provides users with information on the number of requests queued before theirs and an estimated waiting time for their request to be processed. This feature could be implemented as an additional response from the API when a request is made, offering a real-time queue length and an estimated time to completion.
Describe alternatives you've considered
As an alternative, a dashboard or a status page could be made available, where users can see the current load on the server and the average processing time for requests. This would give users a general idea of the waiting period, even if it's not specific to their individual request.
Additional context
This feature would greatly enhance the user experience by providing transparency and allowing for better planning and resource allocation when using cdsapi.
Organisation
Universidade de São Paulo - Institute of Astronomy, Geophysics and Atmospheric Sciences
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Yes, the current issue is the lack of visibility regarding the waiting time for a request to be processed using
cdsapi
. Users are unable to know how long they will have to wait for their request to be run.I find it challenging and inefficient to work with the cdsapi when I'm unable to determine the length of time I'll need to wait for my request to be processed. This uncertainty makes it difficult to plan and manage data retrieval tasks effectively.
Describe the solution you'd like
I would like to see an enhancement in the cdsapi that provides users with information on the number of requests queued before theirs and an estimated waiting time for their request to be processed. This feature could be implemented as an additional response from the API when a request is made, offering a real-time queue length and an estimated time to completion.
Describe alternatives you've considered
As an alternative, a dashboard or a status page could be made available, where users can see the current load on the server and the average processing time for requests. This would give users a general idea of the waiting period, even if it's not specific to their individual request.
Additional context
This feature would greatly enhance the user experience by providing transparency and allowing for better planning and resource allocation when using cdsapi.
Organisation
Universidade de São Paulo - Institute of Astronomy, Geophysics and Atmospheric Sciences
The text was updated successfully, but these errors were encountered: