Skip to content

Update performance benchmarks in README.md#49

Merged
vmelamed merged 2 commits into
mainfrom
docs/update-performance
May 20, 2026
Merged

Update performance benchmarks in README.md#49
vmelamed merged 2 commits into
mainfrom
docs/update-performance

Conversation

@vmelamed

Copy link
Copy Markdown
Owner

Summary

Update performance benchmarks in README.md

Commits

  • docs: update performance benchmarks in README.md

Checklist

  • Commit messages follow Conventional Commits format
  • Tests pass locally, and cover new code and edge cases. Test coverage is above 80%.
  • It is not expected that the performance will degrade by more than 20%
  • Documentation is updated if necessary

Copilot AI review requested due to automatic review settings May 20, 2026 01:55
@github-actions

Copy link
Copy Markdown
Contributor

Summary

Summary
Generated on: 05/19/2026 - 21:56:32
Parser: MultiReport (2x Cobertura)
Assemblies: 2
Classes: 7
Files: 8
Line coverage: 98.3% (355 of 361)
Covered lines: 355
Uncovered lines: 6
Coverable lines: 361
Total lines: 1139
Branch coverage: 91.4% (86 of 94)
Covered branches: 86
Total branches: 94
Method coverage: 100% (53 of 53)
Full method coverage: 92.4% (49 of 53)
Covered methods: 53
Fully covered methods: 49
Total methods: 53
Tag: 528_26136485049

Coverage

UlidTool - 100%
Name Line Branch Method Full method
UlidTool 100% 100% 100% 100%
UlidToolApp 100% 100% 100% 100%
UlidType - 97.7%
Name Line Branch Method Full method
UlidType 97.7% 89.4% 100% 92.1%
vm2.Providers.CryptoRandom 100% 100% 100%
vm2.Providers.PseudoRandom 100% 100% 100%
vm2.Ulid 100% 95.8% 100% 100%
vm2.UlidFactory 100% 100% 100% 100%
vm2.UlidSerialization.NsJson.UlidNsConverter 75% 64.2% 100% 33.3%
vm2.UlidSerialization.SysJson.UlidSysConverter 83.3% 75% 100% 0%

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the README’s Performance section to reflect new BenchmarkDotNet results for ULID parsing, formatting, and generation, intended to keep published performance figures current.

Changes:

  • Replaces the existing benchmark table with updated timing/allocation measurements.
  • Simplifies the benchmark table columns (removing Ratio/RatioSD and some baseline rows).

Comment thread README.md
@github-actions

github-actions Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Summary
Generated on: 05/19/2026 - 22:02:20
Parser: MultiReport (2x Cobertura)
Assemblies: 2
Classes: 7
Files: 8
Line coverage: 98.3% (355 of 361)
Covered lines: 355
Uncovered lines: 6
Coverable lines: 361
Total lines: 1139
Branch coverage: 91.4% (86 of 94)
Covered branches: 86
Total branches: 94
Method coverage: 100% (53 of 53)
Full method coverage: 92.4% (49 of 53)
Covered methods: 53
Fully covered methods: 49
Total methods: 53
Tag: 530_26136665669

Coverage

UlidTool - 100%
Name Line Branch Method Full method
UlidTool 100% 100% 100% 100%
UlidToolApp 100% 100% 100% 100%
UlidType - 97.7%
Name Line Branch Method Full method
UlidType 97.7% 89.4% 100% 92.1%
vm2.Providers.CryptoRandom 100% 100% 100%
vm2.Providers.PseudoRandom 100% 100% 100%
vm2.Ulid 100% 95.8% 100% 100%
vm2.UlidFactory 100% 100% 100% 100%
vm2.UlidSerialization.NsJson.UlidNsConverter 75% 64.2% 100% 33.3%
vm2.UlidSerialization.SysJson.UlidSysConverter 83.3% 75% 100% 0%

@github-actions

Copy link
Copy Markdown
Contributor

🐰 Bencher Report

Branchdocs/update-performance
Testbedubuntu-latest
Click to view all benchmark results
BenchmarkLatencyBenchmark Result
nanoseconds (ns)
(Result Δ%)
Upper Boundary
nanoseconds (ns)
(Limit %)
allocatedBenchmark Result
Measure (units)
(Result Δ%)
Upper Boundary
Measure (units)
(Limit %)
gen1-collectsBenchmark Result
Measure (units)
(Result Δ%)
Upper Boundary
Measure (units)
(Limit %)
gen2-collectsBenchmark Result
Measure (units)
(Result Δ%)
Upper Boundary
Measure (units)
(Limit %)
vm2.UlidType.Benchmarks.Factory_NewUlid📈 view plot
🚷 view threshold
65.84 ns
(+5.90%)Baseline: 62.17 ns
74.60 ns
(88.25%)
📈 view plot
🚷 view threshold
40.00 units
(0.00%)Baseline: 40.00 units
48.00 units
(83.33%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
vm2.UlidType.Benchmarks.Ulid_NewUlid📈 view plot
🚷 view threshold
65.41 ns
(+5.26%)Baseline: 62.14 ns
74.57 ns
(87.72%)
📈 view plot
🚷 view threshold
40.00 units
(0.00%)Baseline: 40.00 units
48.00 units
(83.33%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
vm2.UlidType.Benchmarks.Ulid_Parse_Utf16📈 view plot
🚷 view threshold
68.06 ns
(+6.96%)Baseline: 63.63 ns
76.36 ns
(89.13%)
📈 view plot
🚷 view threshold
40.00 units
(0.00%)Baseline: 40.00 units
48.00 units
(83.33%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
vm2.UlidType.Benchmarks.Ulid_Parse_Utf8📈 view plot
🚷 view threshold
59.06 ns
(+6.83%)Baseline: 55.28 ns
66.34 ns
(89.02%)
📈 view plot
🚷 view threshold
40.00 units
(0.00%)Baseline: 40.00 units
48.00 units
(83.33%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
vm2.UlidType.Benchmarks.Ulid_ToString📈 view plot
🚷 view threshold
48.34 ns
(+3.45%)Baseline: 46.72 ns
56.07 ns
(86.21%)
📈 view plot
🚷 view threshold
80.00 units
(0.00%)Baseline: 80.00 units
96.00 units
(83.33%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
📈 view plot
🚷 view threshold
0.00 units
(0.00%)Baseline: 0.00 units
0.00 units
(0.00%)
🐰 View full continuous benchmarking report in Bencher

@vmelamed vmelamed merged commit af22162 into main May 20, 2026
13 checks passed
@vmelamed vmelamed deleted the docs/update-performance branch May 20, 2026 02:17
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