Replies: 1 comment 8 replies
-
Thanks for opening this @torfjelde . This |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Usage of Zygote.jl in Turing.jl generally comes with a really bad overhead.
I and @willtebbutt had a bit of a look at this a week ago, and it seems quite non-trivial to pin-point exactly what we need to do to make things better.
Hence, I figured we should open a discussion so we can dig into this and keep track of where we are at.
A few things that stick out immediately are:
@model
generates conditionals that, in standard execution, usually compile way. This might not be the case for Zygote.jl and so this is likely causing type-instabilities in the model body.Ref
for thelogp
field, which Zygote just treats asRef{Any}
, which again will cause type-instabilities.I think the following is a good starting-point to determine some first points of attack:
vs. completely without Turing.jl
Manifest
Beta Was this translation helpful? Give feedback.
All reactions