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
On cloud, gp3 with 125 MB/s or 250 MB/s throughput is a general option for applications. Currently, foyer needs to read around 10% data while recovery, with the gp3 throughput limitation, the recovery needs 30s ~ 60s+ to recover 50G data. Which is not acceptable for RW.
As a solution, we can support no data recovery for RW first, then optimize the data format of foyer large object disk cache to make it read less data while recovery.
The text was updated successfully, but these errors were encountered:
This issue has been open for 60 days with no activity.
If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.
You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄
On cloud, gp3 with 125 MB/s or 250 MB/s throughput is a general option for applications. Currently, foyer needs to read around 10% data while recovery, with the gp3 throughput limitation, the recovery needs 30s ~ 60s+ to recover 50G data. Which is not acceptable for RW.
As a solution, we can support no data recovery for RW first, then optimize the data format of foyer large object disk cache to make it read less data while recovery.
The text was updated successfully, but these errors were encountered: