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

[META] Translog Optimisation: Upload .ckp file data as object metadata of .tlog file #13091

Closed
3 tasks done
skumawat2025 opened this issue Apr 5, 2024 · 0 comments
Closed
3 tasks done
Assignees
Labels
Meta Meta issue, not directly linked to a PR Roadmap:Cost/Performance/Scale Project-wide roadmap label Storage:Performance v2.15.0 Issues and PRs related to version 2.15.0

Comments

@skumawat2025
Copy link
Contributor

skumawat2025 commented Apr 5, 2024

Please describe the end goal of this project

Proposing a optimisation for translog files uploads. In this optimisation we purpose a solution to store checkpoint file data as object metadata/header of translog.tlog file for supported cloud providers. The end goal of this is to reduce the rate or number of calls to remote store during translog uploads. In this meta, we will breakdown the issue to smaller issues that we would be working on to complete this feature request.

Supporting References

Feature request - #13022

Issues

Related component

Storage:Performance

@skumawat2025 skumawat2025 added Meta Meta issue, not directly linked to a PR untriaged Storage:Performance v2.14.0 and removed untriaged labels Apr 5, 2024
@skumawat2025 skumawat2025 self-assigned this Apr 5, 2024
@skumawat2025 skumawat2025 added the v2.15.0 Issues and PRs related to version 2.15.0 label May 7, 2024
@andrross andrross added the Roadmap:Cost/Performance/Scale Project-wide roadmap label label May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meta Meta issue, not directly linked to a PR Roadmap:Cost/Performance/Scale Project-wide roadmap label Storage:Performance v2.15.0 Issues and PRs related to version 2.15.0
Projects
Status: 2.15.0 (Release window opens on June 10th, 2024 and closes on June 25th, 2024)
Status: New
Development

No branches or pull requests

2 participants