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 was archived by the owner on Nov 2, 2018. It is now read-only.
Currently, to identify a download in the download queue, siac has to grab the full list of downloads from the api, and then iterate over them. It compares the source and destination for a match to the download that it is looking for, which isn't complete, as you could potentially download the same file to the same destination multiple times.
Instead, when you create a download you should be given a UID for the download that you can use to query the API for information about that download specifically. And then you should have an endpoint which allows you to fetch only that download from the download queue (much less data to receive and iterate over), so that we can make download progress checking more efficient.
This is a particular performance concern because siac requests the download queue repeatedly while it is reporting the progress of a file.
The text was updated successfully, but these errors were encountered:
Currently, to identify a download in the download queue, siac has to grab the full list of downloads from the api, and then iterate over them. It compares the source and destination for a match to the download that it is looking for, which isn't complete, as you could potentially download the same file to the same destination multiple times.
Instead, when you create a download you should be given a UID for the download that you can use to query the API for information about that download specifically. And then you should have an endpoint which allows you to fetch only that download from the download queue (much less data to receive and iterate over), so that we can make download progress checking more efficient.
This is a particular performance concern because siac requests the download queue repeatedly while it is reporting the progress of a file.
The text was updated successfully, but these errors were encountered: