Speed up Kive launches
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
If you're in the middle of running many samples through Kive, and you restart micall_watcher.py, it can take over an hour to get the load back up to the maximum active limit. We made some improvements with #471, but it's still slow. It also seems to speed up and slow down.
Do some profiling to find where the time is spent, but one candidate might be downloading the results from runs that have already completed. When micall_watcher.py restarts, it deletes all the scratch folders so that the results have to be downloaded again. We could wait until the run is finished before downloading all the results, or we could stop deleting the scratch folders, and just check MD5 checksums.
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 with micall_watcher.py and profile restart recovery while many samples are active, focusing on scratch-folder cleanup and downloading results from completed runs. Compare the time spent in those paths and verify that restarting restores the active limit without unnecessary result downloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100