Skip to content

Commit 276916a

Browse files
authored
documenting behavior when used with Base.Threads
Adding a note to the docs on loss of performance when Octavian is combined with Base.Threads.
1 parent 49673bc commit 276916a

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/src/index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,9 @@ In general:
2525
- Octavian has the fastest CPU performance.
2626
- GemmKernels has the fastest GPU performance.
2727
- Tullio is the most flexible.
28+
29+
!!! note
30+
31+
Octavian's tasks can interfere with tasks spawned by Base.Threads, resulting in much slower execution times when used together. This can be avoided by using threading utilities from [CheapThreads](https://github.com/JuliaSIMD/CheapThreads.jl) or [LoopVectorization](https://github.com/JuliaSIMD/LoopVectorization.jl/) instead. See this [Discourse post](https://discourse.julialang.org/t/odd-benchmarktools-timings-using-threads-and-octavian/59838) for more information.
32+
33+

0 commit comments

Comments
 (0)