toonarmycaptain / toonarmycaptain/parseplot
Parser efficiency for large umbers of points
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Parser is very slow for large numbers of points.
500 points takes 3-4 sec, 5000 can take 40+ seconds.
Hopefully there is some sort of efficiency to be gained, maybe some parallelism?
Bottleneck appears to be the parser, but how to pull the parsed expression out as a python function/expression, rather than reevaluating the string with new variable values interpolated?
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 examining the parser bottleneck identified in commit 774b997b23b7770219edd6a0f80cf8cdbb8e0b56 and reproduce the reported timings with 500 and 5,000 points. Determine whether parsing or repeated expression evaluation dominates, then verify that the plotting behavior is unchanged and the larger input completes substantially faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100