pymc-devs / pymc-devs/pytensor
Two parametrization of JAX benchmark test are taking hours
Open
Nobody has claimed this yet.
jax
needs info
tests
- Dominant language
- Python
- Stars
- 644
- Forks
- 208
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 16
Description
Description
I thought that there was a problem in a recent PR I did, but I found others passed after HOURS 🗡️
Need to check if there was a recent regression introduced by us or JAX
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
Start with the JAX benchmark test and its two parametrizations, then compare their runtime with the recent PR and the JAX version in use. Reproduce the multi-hour execution and determine whether the regression comes from PyTensor or JAX; done means identifying the cause and confirming a reasonable runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100