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
This has been discussed in the context of autoretrieve for some time now but I think originally they were all set to true but now it appears Boost has this wired up so keep-unsealed-copy config = FastRetrieval metadata.
FastRetrieval = true entries should get priority in the queryCompare function for the prioritywaitqueue when we have multiple queries returned and waiting for attempts.
Questions:
Should prioritisation be even higher than this? If candidate A is FastRetrieval=false and B is FastRetrieval=true and A returns its query first, should we hold off on attempting a retrieval and give B a chance to come back first?
Perhaps we should shorten the first-byte timeout for FastRetrieval=false candidates under the assumption that they may be attempting an unseal?
If we have >X candidates and some high percentage of them are FastRetrieval=true, perhaps we should filter out the others and only attempt the ones we assume have unsealed copies? e.g. 10 candidates for a CID, 7 of them are FastRetrieval=false, don't even bother attempting the other 3?
The text was updated successfully, but these errors were encountered:
From #35 (comment)
This has been discussed in the context of autoretrieve for some time now but I think originally they were all set to
true
but now it appears Boost has this wired up so keep-unsealed-copy config =FastRetrieval
metadata.How:
Metadata
field from the indexer results is base64 (padded) encoded varint-prefixed dag-cbor which can be decoded via https://github.com/ipni/index-provider/blob/19931fd5c692e5efd38093c1764cf0a3ca464af4/metadata/graphsync_filecoinv1.go#L66FastRetrieval = true
entries should get priority in thequeryCompare
function for the prioritywaitqueue when we have multiple queries returned and waiting for attempts.Questions:
FastRetrieval=false
and B isFastRetrieval=true
and A returns its query first, should we hold off on attempting a retrieval and give B a chance to come back first?FastRetrieval=false
candidates under the assumption that they may be attempting an unseal?FastRetrieval=true
, perhaps we should filter out the others and only attempt the ones we assume have unsealed copies? e.g. 10 candidates for a CID, 7 of them areFastRetrieval=false
, don't even bother attempting the other 3?The text was updated successfully, but these errors were encountered: