Is this supposed to be surprising? Try streaming video transcoding or 3D rendering and I'm pretty sure you get the opposite result. Some workloads perform better in one than the other. My guess would be that filesystem and IO latency is a major factor in these results.
Go has been optimized for Linux moreso than macOS.
Also, as noted in the thread:
> The time (210ms) is too short for a meaningful benchmark because initialization and the like are overshadowing the work done. You need a test with 100 times more pages.
Go has been optimized for Linux moreso than macOS.
Also, as noted in the thread:
> The time (210ms) is too short for a meaningful benchmark because initialization and the like are overshadowing the work done. You need a test with 100 times more pages.