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 Aug 8, 2023. It is now read-only.
Offline downloads can produce a large number of concurrent requests, bloating memory, overloading the network connection, and causing many of the requests to time out. In order to avoid these problems, OnlineFileSource should throttle concurrent requests at a reasonable number, placing throttled requests in a queue for execution once existing requests have completed.
This could be implemented in the offline code itself, but I think it makes more sense in OnlineFileSource, because there could be non-offline corner cases that also generate a large number of simultaneous requests, for example with huge screens. These should also be throttled.
The text was updated successfully, but these errors were encountered:
Offline downloads can produce a large number of concurrent requests, bloating memory, overloading the network connection, and causing many of the requests to time out. In order to avoid these problems, OnlineFileSource should throttle concurrent requests at a reasonable number, placing throttled requests in a queue for execution once existing requests have completed.
This could be implemented in the offline code itself, but I think it makes more sense in OnlineFileSource, because there could be non-offline corner cases that also generate a large number of simultaneous requests, for example with huge screens. These should also be throttled.
The text was updated successfully, but these errors were encountered: