Skip to content

👑 Reduce memory footprint for LocalDB #11514

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.

Sign up for GitHub

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

Jump to bottom
Open
Tracked by #11606
kunga opened this issue Nov 12, 2024 · 0 comments
Open
Tracked by #11606

👑 Reduce memory footprint for LocalDB #11514

kunga opened this issue Nov 12, 2024 · 0 comments
Assignees
@kunga
Labels
area/datashard Issues related to datashard tablets (relational table partitions)

Comments

@kunga
Copy link
Member

kunga commented Nov 12, 2024

Description

In addition to #1483 we need to address some other Local Database data structures that now are required to be kept in memory.

This improvement reduces memory requirements for storing "cold" data.

Steps

1. Inline TMeta data structure into TPageId

Instead of storing a separate TMeta, place page's offsets and auxiliary flags directly into TPageId.

Internal design doc.
@kunga kunga self-assigned this Nov 12, 2024
@kunga kunga added this to 👑 Epics Nov 12, 2024
@kunga kunga moved this to Planned in 👑 Epics Nov 12, 2024
@kunga kunga mentioned this issue Nov 14, 2024
Open
13 tasks
@kunga kunga added the area/datashard Issues related to datashard tablets (relational table partitions) label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kunga kunga

Labels
area/datashard Issues related to datashard tablets (relational table partitions)
Projects
👑 Epics
Status: Planned
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kunga