Running time optimization
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 22
- Forks
- 6
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
I did a profiling of prepare_ae_forstly, format_ae_forestly and ae_forestly and here is the profiling results:
Related issues: https://github.com/Merck/forestly/issues/148
Contributor guide
No contributing guide indexed for this repository
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 by locating prepare_ae_forstly, format_ae_forestly, and ae_forestly, then reproduce the profiling results shown in the issue. Read related issue #148 for the intended optimization scope; done should mean the targeted runtime bottleneck is improved without changing the functions' expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100