google/gvisor

sentry/time: consider a sequence number of read locking

Open

#181 opened on Apr 3, 2019

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Go (1,061 forks)batch import
exportedgood first issuepriority: p3type: cleanup

Repository metrics

Stars
 (12,713 stars)
PR merge metrics
 (PR metrics pending)

Description

This could avoid taking a lock in CalibratedClocks.GetTime.

Contributor guide

Research direction
Investigate the use of sequence numbers as an alternative to locking in CalibratedClocks.GetTime. Study the current locking mechanism and design a sequence number based approach to avoid contention.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Goconcurrencylocking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65