pymc-devs / pymc-devs/pytensor
Add test for benchmarking import time
Open
Nobody has claimed this yet.
GitHub CI/CD
performance
tests
- Dominant language
- Python
- Stars
- 644
- Forks
- 208
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 16
Description
Description
We did some work recently to cut down PyTensor import time. We should protect against unnoticed regressions by testing explicitly. Not sure this can be done inside a pytest/python environment or if we need a custom job in the CI for it that makes use of python -X importtime command
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 existing pytest and CI setup, then investigate Python's -X importtime entry point for measuring PyTensor import time. Decide whether the regression check belongs in pytest or a dedicated CI job; done means import-time regressions are detected automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100