pingcap / pingcap/tiflash

Memory optimization for empty tables and empty segments

Open
#8,051 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/storage type/enhancement
Dominant language
C++
Stars
1k
Forks
423
Avg merge
1d 15h
Merged PRs (30d)
24

Description

Enhancement

Currently, we don't clean the empty tables and empty segments thoroughly. Thus, there's a lot of completely useless memory after tiflash scaling-out or other normally region transfering.

In order to optimize the memory usage, we need to cut down the memory usage of empty tables and segments as possible as we can.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing how empty tables and segments are retained after scaling out or region transfers, then define measurable memory behavior before changing cleanup. Done means empty tables and segments no longer retain unnecessary memory.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
databases, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.