ash/eskit
1
0
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions 2

Benchmark Postgres sequence gap strategies #8

New issue
Open
opened 2026-02-19 21:28:02 +00:00 by ash · 0 comments
ash commented 2026-02-19 21:28:02 +00:00
Owner
Copy link

What

Benchmark all 4 approaches to the sequence gap problem with real Postgres on VPS.

Strategies

  1. Single writer (baseline — no gaps)
  2. Published sequence table (extra write, trivial reads)
  3. pg_snapshot / xmin visibility (correct but unknown perf)
  4. Gap detection with timeout (generic fallback)

Method

  • 1M events in table
  • Concurrent writers (10 goroutines)
  • Measure: read latency, write overhead, gap detection accuracy
  • Test with held-open transactions
  • p50/p95/p99 latencies

VPS: 143.14.50.71

## What Benchmark all 4 approaches to the sequence gap problem with real Postgres on VPS. ## Strategies 1. Single writer (baseline — no gaps) 2. Published sequence table (extra write, trivial reads) 3. pg_snapshot / xmin visibility (correct but unknown perf) 4. Gap detection with timeout (generic fallback) ## Method - 1M events in table - Concurrent writers (10 goroutines) - Measure: read latency, write overhead, gap detection accuracy - Test with held-open transactions - p50/p95/p99 latencies ## VPS: 143.14.50.71
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
bug

   
documentation

   
enhancement

   
investigation

   
performance

   
production-ready

   
testing
No labels
bug
documentation
enhancement
investigation
performance
production-ready
testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ash/eskit#8
No description provided.