yugabyte/yugabyte-db

[YSQL] Benchmark the latency impact of calling clockbound lib.

Closed

#24,401 opened on Oct 11, 2024

View on GitHub
 (0 comments) (0 reactions) (1 assignee)C (1,003 forks)batch import
area/ysqlgood first issuekind/enhancementpriority/low

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-13310

Description

WallClock retrieves time directly from shared memory.

However, ClockboundClock needs to acquire a mutex and then do some processing in the library call to extract time and its bounds.

Good to benchmark the impact of this change.

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

Contributor guide

Research direction
The issue asks to benchmark the latency impact of using ClockboundClock instead of WallClock. First, locate the source files for WallClock and ClockboundClock (likely in src/yb/clock/). Then design a benchmark that measures time retrieval latency under varying concurrency levels. Implement the benchmark in C, run it on the same hardware, and record results. Compare the overhead of mutex acquisition and processing in ClockboundClock. Provide a summary of findings with recommendations.
Tech stack
c
Domain
databaseperformance
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C programmingbenchmarking experienceunderstanding of clock synchronization
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15