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
Are there any mistakes in the docs?
Some notebooks (e.g. https://gpflow.github.io/GPflow/develop/notebooks/advanced/natural_gradients.html, there may be more, I did not check extensively) do not use @tf.function when using a non-Scipy optimizer (our Scipy class automatically wraps the optimisation in tf.function by default). This is significantly slower in practice, and for any real data sets you would want to ensure the tf.function-precompilation. The notebooks should demonstrate this best practice, so users do not wonder why GPflow is so slow...
The text was updated successfully, but these errors were encountered:
st--
changed the title
Demonstrate best practices in the notebooks
Demonstrate best practices in the notebooks: @tf.functionDec 8, 2022
Documentation/tutorial notebooks
Are there any mistakes in the docs?
Some notebooks (e.g. https://gpflow.github.io/GPflow/develop/notebooks/advanced/natural_gradients.html, there may be more, I did not check extensively) do not use
@tf.function
when using a non-Scipy
optimizer (ourScipy
class automatically wraps the optimisation in tf.function by default). This is significantly slower in practice, and for any real data sets you would want to ensure the tf.function-precompilation. The notebooks should demonstrate this best practice, so users do not wonder why GPflow is so slow...The text was updated successfully, but these errors were encountered: