Open judober opened 1 year ago
Hmm, can't reproduce on 1.9.2 on mac (maybe os-specific?), but does max out cpu for a minute when Julia is started with #threads = #cores (vs returning more or less instantly when Julia is started with only a single thread)
It may be worth opening an issue on https://github.com/JuliaMath/FFTW.jl if you haven't already
Yes, I opend issue 275 in FFTW (as linked in the opening post)
As for the os, I may be able to try macos myself to have another data point. What CPU are you using?
julia> versioninfo()
Julia Version 1.9.2
Commit e4ee485e909 (2023-07-05 09:39 UTC)
Platform Info:
OS: macOS (arm64-apple-darwin22.4.0)
CPU: 10 × Apple M1 Max
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-14.0.6 (ORCJIT, apple-m1)
Threads: 1 on 8 virtual cores
Hmm, can't reproduce on 1.9.2 on mac (maybe os-specific?), but does max out cpu for a minute when Julia is started with #threads = #cores (vs returning more or less instantly when Julia is started with only a single thread)
I can confirm this behaviour on a similar setup:
julia> versioninfo()
Julia Version 1.9.2
Commit e4ee485e909 (2023-07-05 09:39 UTC)
Platform Info:
OS: macOS (arm64-apple-darwin22.4.0)
CPU: 8 × Apple M1 Pro
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-14.0.6 (ORCJIT, apple-m1)
Threads: 8 on 6 virtual cores
I can also confirm this behaviour with FFTW 1.7.2 and Julia 1.10 on Windows.
julia> versioninfo()
Julia Version 1.10.0
Commit 3120989f39 (2023-12-25 18:01 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: 28 × Intel(R) Xeon(R) W-2275 CPU @ 3.30GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-15.0.7 (ORCJIT, cascadelake)
Threads: 20 on 28 virtual cores
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS = 14
The code (fairly reduced)
results in this access violation:
when julia is started with
julia --threads="auto" --startup-file="no"
on windows.with FFTW 1.7.1
Either reducting the threads for FFTW or starting julia without threads solves this issue.
I'm not shure if this belongs here or in FFTW. I posted the issue there too.