Skip to content

Conversation

@g3co
Copy link
Contributor

@g3co g3co commented Feb 11, 2026

No description provided.

@g3co g3co requested a review from TrueCarry February 11, 2026 10:20
@github-actions
Copy link

github-actions bot commented Feb 11, 2026

📊 Performance Metrics

Performance Metrics (memory storage)

  • CPU: 0.75s (4 cores) • Goroutines: 8 • Threads: 7
  • Memory: 12.5MB heap • 43.6MB RAM • 35.9MB total • 238598 allocs
  • GC: 12 cycles (0.60ms avg)
  • FDs: 9/65536 (0.0%)

@github-actions
Copy link

github-actions bot commented Feb 11, 2026

📊 Performance Metrics

Performance Metrics (postgres storage)

  • CPU: 0.85s (4 cores) • Goroutines: 10 • Threads: 9
  • Memory: 19.3MB heap • 58.9MB RAM • 40.7MB total • 267997 allocs
  • GC: 10 cycles (0.43ms avg)
  • FDs: 35/65536 (0.1%)

@github-actions
Copy link

github-actions bot commented Feb 11, 2026

📊 Performance Metrics

Performance Metrics (cluster-valkey storage)

  • CPU: 0.70s (4 cores) • Goroutines: 11 • Threads: 10
  • Memory: 21.7MB heap • 54.1MB RAM • 33.7MB total • 294308 allocs
  • GC: 8 cycles (0.36ms avg)
  • FDs: 71/65536 (0.1%)

@github-actions
Copy link

github-actions bot commented Feb 11, 2026

📊 Performance Metrics

Performance Metrics (nginx storage)

  • CPU: 0.08s (4 cores) • Goroutines: 6 • Threads: 6
  • Memory: 1.1MB heap • 20.9MB RAM • 1.1MB total • 6160 allocs
  • GC: 0 cycles (0ms avg)
  • FDs: 14/65536 (0.0%)

@github-actions
Copy link

github-actions bot commented Feb 11, 2026

📊 Performance Metrics

Performance Metrics (dnsmasq storage)

  • CPU: 0.24s (4 cores) • Goroutines: 11 • Threads: 9
  • Memory: 5.6MB heap • 31.6MB RAM • 13.8MB total • 69616 allocs
  • GC: 6 cycles (0.21ms avg)
  • FDs: 61/65536 (0.1%)

@g3co g3co merged commit 1e441f3 into master Feb 12, 2026
12 checks passed
@g3co g3co deleted the dev/upgrade_go126 branch February 12, 2026 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants