stan-dev / stan-dev/rstantools
Slow package building with rstan 2.26.23
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 48
- Forks
- 24
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 1
Description
> happens with the rstantools configure script disabled too, and no compilation occurring, fyi.
This is because we're using a less powerful javascript engine (quickjs instead of V8) which is more portable, but less performant.
There were significant optimisations in
stanc3after 2.26, so once we getStanHeaders2.32 on CRAN then the parsing time should be ~3x fasterOriginally posted by @andrjohns in https://github.com/stan-dev/rstan/issues/1084#issuecomment-1711756010
If I've disabled the configure script of rstantools in my package, and the binaries are already built, is it true that parsing is still occurring? if so, can it be turned off somehow? I realise the aim is to get rstan 2.32 out quickly, but forgive me if I don't have full faith there ;) and even 3x faster will still be annoying for package dev...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the rstantools configure script and package-build path, comparing behavior when the script is disabled and binaries are already built. Determine whether parsing still occurs and whether a supported way to disable it exists; done means the behavior and package-build impact are confirmed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, r
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100