3 ms·
I’m curious how this looks on ARM64. (Sorry, Aarch64.). x86 context switches are overcomplicated and inherently slow.
by amluto 6y ago
I’m curious how this looks on ARM64. (Sorry, Aarch64.). x86 context switches are overcomplicated and inherently slow.
- lstamour 6y agoWell, here's what it looked like on my MacBook Pro with M1/16GB: M1-MBP async-brigade % time cargo run --release 500 tasks, 10000 iterations: mean 761.403µs per iteration, stddev 8.929µs (1.522µs per task per iter) cargo run --release 3.21s user 4.60s system 99% cpu 7.818 total M1-MBP thread-brigade % time cargo run --release 500 tasks, 10000 iterations: mean 787.149µs per iteration, stddev 67.289µs (1.574µs per task per iter) cargo run --release 0.94s user 7.19s system 100% cpu 8.081 total I ran it a few times and the numbers came up rather similar each time: async-brigade finished in 760.273µs-764.928µs while thread-brigade took 784.510µs-796.323µs. As macOS doesn't have taskset, I can't easily set affinity. I tried to use the workaround documented elsewhere to use Xcode's Instruments to reduce the number of CPU cores but it would always re-enable itself at 8 cores, so that didn't work.