Closed cgarling closed 1 year ago
This is annoying enough that I'm disabling threading on these functions. Keeping the issue open in case we want to revisit in the future.
Now looking like we probably don't want to thread these functions anyway. We can thread at a higher level (e.g., by using sampling methods).
It seems we get reasonable scaling out of setting
thread=true
forLoopVectorization.@turbo
in the basic functionsloglikelihood
,∇loglikelihood
, and∇loglikelihood!
but it currently breaks the parallelhmc_sample
method when used with matplotlib due to some GIL error on the python side.