galaxyproject / galaxyproject/galaxy
History copying optimization and/or UX improvement
Open
area/performance
area/UI-UX
kind/refactoring
status/planning
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 169
Description
> if you have a sufficiently large collection (in my case 300+ datasets) it takes >10 min to copy it into a new history. crazy
edit:
Related to: #2526
> [nekrut] but process continues in the background, so eventially it does get copied, but why soooooooooo long?
Contributor guide
Research direction
Reproduce copying a history containing 300 or more datasets and compare the behavior described in the issue. Review related issue #2526 and clarify whether the accepted outcome is faster copying, improved progress feedback, or both; done should be a measurable improvement or clearly communicated background progress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100