Conversation
CodSpeed Performance ReportMerging #173 will not alter performanceComparing Summary
Benchmarks breakdown
Footnotes
|
f75b4cd to
51a110a
Compare
|
Do you know why the benchmarks give so many warnings about system calls? |
Not sure, I reckon it has to do with OpenMP overhead to coordinate the threads. The benchmark mode used runs the code in a virtual CPU and it looks like syscalls are a relevant factor. It's also possible to use wallclock time for the benchmarks, but I am not sure at this stage if there's any benefit for us here. If you enable the syscalls in the flame graphs, you can see e.g. that |
This PR adds threaded versions of the existing NDFT benchmarks.
I have removed the non-OpenMP build jobs where an OpenMP version is available since building with OpenMP is only additive. There's no benefit of keeping the non-OpenMP jobs because we will now just run multi-threaded benchmarks if possible, in addition to the regular ones.