vmware / vmware/splinterdb

Add tracing to `memtable.c`

Open
#124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
732
Forks
67
PR merge metrics
No merged PRs in 30d

Description

We don't have a general tracing framework, but there is also no tracing that occurs when memtables are initialized, etc.

Contributor guide

Open the contributing guide

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

Start by reading memtable.c and identifying where memtables are initialized and where other lifecycle events occur. The issue notes that no general tracing framework exists, so first determine the intended tracing scope and framework before implementation. Done should include tracing for memtable initialization and the agreed related events.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
observability
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.