-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First run is always very slow to start (Windows) #1
Comments
I've reworked the handling of multiple/parallel chains to avoid the use of a mutex/locking when accessing the R session, can you try with the current Also just to flag that I've changed the |
The problem still persists, unfortunately. But now I can kill the function without killing the R process. |
Should be resolved in |
Splendid! Can confirm! |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using R 4.3.2, and the latest version of the package.
This is how it looks when I run e.g.
stan_sample
for the first time in a session:As the log indicates, it is not the sampling that takes 7 minutes, but something else. The main waiting time is before the first "Gradient evaluation took xxx". If I run any of the functions again, it doesn't have any waiting time like this, regardless of data and loglikelihood function.
The text was updated successfully, but these errors were encountered: