Skip to content

Conversation

cagatay-y
Copy link
Contributor

No description provided.

@mkroening mkroening self-assigned this Oct 16, 2025
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Benchmark Results

Benchmark Current: e5259b5 Previous: c6484a7 Performance Ratio
startup_benchmark Build Time 112.64 s 109.12 s 1.03
startup_benchmark File Size 0.90 MB 0.90 MB 1.00
Startup Time - 1 core 0.92 s (±0.04 s) 0.88 s (±0.02 s) 1.04
Startup Time - 2 cores 0.91 s (±0.03 s) 0.87 s (±0.02 s) 1.04
Startup Time - 4 cores 0.92 s (±0.03 s) 0.87 s (±0.03 s) 1.06
multithreaded_benchmark Build Time 116.41 s 104.93 s 1.11
multithreaded_benchmark File Size 1.01 MB 1.01 MB 1.00
Multithreaded Pi Efficiency - 2 Threads 90.11 % (±8.27 %) 3.66 % (±17.59 %) 24.59
Multithreaded Pi Efficiency - 4 Threads 44.02 % (±3.93 %) 1.91 % (±9.18 %) 23.02
Multithreaded Pi Efficiency - 8 Threads 25.71 % (±2.15 %) 1.02 % (±4.90 %) 25.19
micro_benchmarks Build Time 114.41 s 102.53 s 1.12
micro_benchmarks File Size 1.01 MB 1.01 MB 1.00
Scheduling time - 1 thread 71.20 ticks (±4.86 ticks) 2.54 ticks (±12.22 ticks) 27.98
Scheduling time - 2 threads 41.17 ticks (±6.30 ticks) 1.29 ticks (±6.17 ticks) 32.02
Micro - Time for syscall (getpid) 3.31 ticks (±0.40 ticks) 0.11 ticks (±0.53 ticks) 30.02
Memcpy speed - (built_in) block size 4096 80757.70 MByte/s (±55712.37 MByte/s) 1662.23 MByte/s (±7978.72 MByte/s) 48.58
Memcpy speed - (built_in) block size 1048576 42755.53 MByte/s (±29599.36 MByte/s) 802.31 MByte/s (±3851.09 MByte/s) 53.29
Memcpy speed - (built_in) block size 16777216 24174.86 MByte/s (±20026.37 MByte/s) 231.25 MByte/s (±1110.01 MByte/s) 104.54
Memset speed - (built_in) block size 4096 80815.84 MByte/s (±55757.14 MByte/s) 1875.00 MByte/s (±9000.00 MByte/s) 43.10
Memset speed - (built_in) block size 1048576 42994.23 MByte/s (±29767.97 MByte/s) 1009.80 MByte/s (±4847.02 MByte/s) 42.58
Memset speed - (built_in) block size 16777216 24972.62 MByte/s (±20595.92 MByte/s) 995.24 MByte/s (±4777.13 MByte/s) 25.09
Memcpy speed - (rust) block size 4096 69488.50 MByte/s (±48725.85 MByte/s) 1463.41 MByte/s (±7024.39 MByte/s) 47.48
Memcpy speed - (rust) block size 1048576 42194.94 MByte/s (±29244.82 MByte/s) 795.04 MByte/s (±3816.19 MByte/s) 53.07
Memcpy speed - (rust) block size 16777216 24731.70 MByte/s (±20571.65 MByte/s) 236.47 MByte/s (±1135.06 MByte/s) 104.59
Memset speed - (rust) block size 4096 69934.93 MByte/s (±49077.38 MByte/s) 1846.15 MByte/s (±8861.54 MByte/s) 37.88
Memset speed - (rust) block size 1048576 42449.07 MByte/s (±29427.95 MByte/s) 1016.88 MByte/s (±4881.03 MByte/s) 41.74
Memset speed - (rust) block size 16777216 25513.07 MByte/s (±21117.46 MByte/s) 993.35 MByte/s (±4768.08 MByte/s) 25.68
alloc_benchmarks Build Time 114.69 s 100.75 s 1.14
alloc_benchmarks File Size 0.97 MB 0.97 MB 1.00
Allocations - Allocation success 100.00 % 2.00 % (±13.86 %) 50
Allocations - Deallocation success 69.95 % (±0.25 %) 1.40 % (±9.73 %) 49.81
Allocations - Pre-fail Allocations 100.00 % 2.00 % (±13.86 %) 50
Allocations - Average Allocation time 12408.25 Ticks (±327.38 Ticks) 229.53 Ticks (±1590.58 Ticks) 54.06
Allocations - Average Allocation time (no fail) 12408.25 Ticks (±327.38 Ticks) 229.53 Ticks (±1590.58 Ticks) 54.06
Allocations - Average Deallocation time 752.86 Ticks (±80.09 Ticks) 13.15 Ticks (±91.10 Ticks) 57.27
mutex_benchmark Build Time 110.47 s 101.46 s 1.09
mutex_benchmark File Size 1.01 MB 1.01 MB 1.00
Mutex Stress Test Average Time per Iteration - 1 Threads 13.08 ns (±0.74 ns) 0.24 ns (±1.66 ns) 54.50
Mutex Stress Test Average Time per Iteration - 2 Threads 15.20 ns (±1.52 ns) 0.26 ns (±1.80 ns) 58.46

This comment was automatically generated by workflow using github-action-benchmark.

Copy link
Member

@mkroening mkroening left a comment

Choose a reason for hiding this comment

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

Looks good, thanks! :)

Would it make sense to log these as errors instead of warnings?

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