pymc-devs / pymc-devs/pytensor
ENH: Benchmark different backends and compare them to pure implementations
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Python
- Stars
- 644
- Forks
- 208
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 16
Description
Context for the issue:
Add an example of how Pytensor backend switching compares to a pure implementation in that backend.
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
The issue names Pytensor backend switching and pure implementations but no file, test, or benchmark entry point. First locate existing backend-switching examples and benchmark infrastructure, then compare a Pytensor implementation with the corresponding pure backend implementation; done means the example clearly reports both results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100