NetLogo / NetLogo/Python-Extension
Optimize py:set by batching
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 31
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Currently, every py:set sends a message to the python process and waits for a result. However, we could instead batch py:sets with py:runs and py:runresults to reduce the amount of communication. This would likely be a pretty good performance boost, as communication time is definitely a big bottleneck.
Copied from: https://github.com/qiemem/PythonExtension/issues/10
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
No files or tests are named. Start by tracing the py:set, py:run, and py:runresult entry points and the communication with the Python process; done means py:set operations are batched with the run and runresult flow to reduce communication overhead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, scala
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100