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
Knowing how long a URL has spent in the queues is very useful and a good addition to knowing how long the actual fetching took. This could be used for instance to throttle the emissions of URLs from a particular backend, similar to #504. These also reflect the robots wait directives - as well as the actual waiting time for the queue.
This should also be provided as metrics.
The text was updated successfully, but these errors were encountered:
Knowing how long a URL has spent in the queues is very useful and a good addition to knowing how long the actual fetching took. This could be used for instance to throttle the emissions of URLs from a particular backend, similar to #504. These also reflect the robots wait directives - as well as the actual waiting time for the queue.
This should also be provided as metrics.
The text was updated successfully, but these errors were encountered: