You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On MacOS I consistently get 99.9% mem usage, like in the following report (part of it)
test/distributions/normal_family/mv_normal_weighted_mean_precision_tests.jl:72
Worker 2006: 10:52:43 | maxrss 2.7% | mem 99.7% | DONE ( 32/187) test item "MvNormalWeightedMeanPrecision: vague" 0.3 secs (8.9% compile), 76.22 K allocs (4.366 MB)
Worker 2008: 10:52:43 | maxrss 4.7% | mem 99.9% | DONE ( 19/187) test item "InverseWishart: mean(::typeof(logdet))" 6.6 secs (12.3% compile, 9.5% GC), 16.84 M allocs (1.626 GB)
Worker 2006: 10:52:43 | maxrss 2.7% | mem 99.9% | START ( 33/187) test item "MvNormalWeightedMeanPrecision: prod" at test/distributions/normal_family/mv_normal_weighted_mean_precision_tests.jl:92
which shows 99.9% memory use for all tests, even small and even those which do not allocate at all. GitHub Actions CI shows mem at about 30-40%.
In the system settings I can see that I have plenty of RAM available, more than 8GB (out of 16) are free during the tests. My guess is that mem computation is wrong on MacOS. This issue basically forces to use memory_threshold = 1.0 on MacOS, otherwise all workers are killed and restarted after each test.
julia>versioninfo()
Julia Version 1.9.3
Commit bed2cd540a1 (2023-08-2414:43 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: macOS (x86_64-apple-darwin22.4.0)
CPU:12×Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
WORD_SIZE:64
LIBM: libopenlibm
LLVM: libLLVM-14.0.6 (ORCJIT, skylake)
Threads:1 on 12 virtual cores
The text was updated successfully, but these errors were encountered:
AFAIK memory management system in MacOS is different from Linux and it can easily report 99% case, but it does not mean that the memory is not available, it simply means that most of its reserved for idle applications but it still can be used. Not sure if it can be fixed easily. Maybe it should be documented more clearly.
On MacOS I consistently get
99.9%
mem usage, like in the following report (part of it)which shows
99.9%
memory use for all tests, even small and even those which do not allocate at all. GitHub Actions CI shows mem at about30-40%
.In the system settings I can see that I have plenty of RAM available, more than 8GB (out of 16) are free during the tests. My guess is that mem computation is wrong on MacOS. This issue basically forces to use
memory_threshold = 1.0
on MacOS, otherwise all workers are killed and restarted after each test.The text was updated successfully, but these errors were encountered: