nviennot/core-to-core-latency

Garbled results on Windows 11

khromov opened this issue · 1 comments

khromov commented

Example run below. Same results in cmd.exe and PowerShell.

>core-to-core-latency.exe
Num cores: 8
Using RDTSC to measure time: false
Num round trips per samples: 1000
Num samples: 300
Showing latency=round-trip-time/2 in nanoseconds:

       0       1       2       3       4       5       6       7
  0
  1 ←[1;37m   0←[0m←[2;37m±0 ←[0m
  2 ←[1;37m  52←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m
  3 ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m   0←[0m←[2;37m±0 ←[0m
  4 ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  25←[0m←[2;37m±6 ←[0m ←[1;37m  53←[0m←[2;37m±6 ←[0m
  5 ←[1;37m  25←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  25←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  25←[0m←[2;37m±6 ←[0m
  6 ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  52←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  25←[0m←[2;37m±6 ←[0m ←[1;37m  25←[0m←[2;37m±6 ←[0m
  7 ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  25←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  27←[0m←[2;37m±6 ←[0m ←[1;37m  25←[0m←[2;37m±6 ←[0m ←[1;37m   0←[0m←[2;37m±0 ←[0m

Min  latency: ←[1;37m0.0←[0mns ←[2;37m±0.0←[0m cores: (1,0)
Max  latency: ←[1;37m53.3←[0mns ←[2;37m±37.6←[0m cores: (4,3)
Mean latency: ←[1;37m26.1←[0mns

It does work in WSL2 though.

nviennot commented

A nicer output can be obtained by adding --csv > output.csv

  • 👍1