Optimize snapshot_gc_scn access by moving to memory
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 342
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 53
Description
Description
During idle load analysis, it was observed that there is a high volume of accesses to the snapshot_gc_scn value via physical tables. Analysis indicates that in a single-server environment, the snapshot_gc_scn no longer needs to be stored in a physical table. It can be modified to reside in memory.
Proposed Solution
Change the storage of snapshot_gc_scn from a persistent table to an in-memory value for single-server deployments.
Context
This is an internal SQL optimization task.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the snapshot_gc_scn storage and access paths in the C++ database code, then trace how single-server deployments use the value. Confirm the relevant persistence and in-memory paths before changing anything; done means single-server access no longer requires the physical table while the value remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, sql
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100