Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Break down retrieval success rate by Deals, Clients, Allocators, MetaAllocators #139

Open
Tracked by #131
patrickwoodhead opened this issue Jul 24, 2024 · 2 comments
Assignees

Comments

@patrickwoodhead
Copy link

patrickwoodhead commented Jul 24, 2024

eta: 2024-09-30

Currently, the Spark Retrieval Success Rate (RSR) is aggregated by Storage Provider. This gives us a Spark score for each Storage Provider. However, there are different personas in the FIL+ community who would be interested in seeing the RSR of Filecoin aggregated differently.

Firstly, there is the breakdown by deals. Since Spark is based on payload CID rather than piece CID, there might be multiple retrieval tasks in the same deal. It would be great to see the Spark RSR and the error breakdown by deal.

Secondly, it would be great to see the Spark RSR aggregated by the clients making the deals. Clients have a responsibility in the datacap flow to allocate their allowance as best they can. The allocators would like to be able to see the performance, including the RSR, aggregated by client

Thirdly, moving up a level, meta-allocators and root key holders would like to see the RSR of all deals linked to allocators and meta-allocators.

@patrickwoodhead patrickwoodhead mentioned this issue Jul 24, 2024
36 tasks
@bajtos bajtos mentioned this issue Jul 26, 2024
@patrickwoodhead patrickwoodhead changed the title Break down retrieval success rate by deals Break down retrieval success rate by Deals, Clients, Allocators, MetaAllocators Jul 26, 2024
@patrickwoodhead patrickwoodhead mentioned this issue Sep 3, 2024
22 tasks
@bajtos
Copy link
Member

bajtos commented Sep 3, 2024

Firstly, there is the breakdown by deals. Since Spark is based on payload CID rather than piece CID, there might be multiple retrieval tasks in the same deal. It would be great to see the Spark RSR and the error breakdown by deal.

See:

@bajtos
Copy link
Member

bajtos commented Dec 2, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants