nspcc-dev / nspcc-dev/neofs-node
Optimize receiving parity parts when GET
Open
Nobody has claimed this yet.
enhancement
I3
neofs-storage
performance
S3
U3
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Originally posted by @cthulhu-rider in https://github.com/nspcc-dev/neofs-node/pull/3497#discussion_r2329485123
it's proposed to not create new goroutine when it is definitely necessary to download redundant parts. In terms of code - try to combine for-loops, at least partially
Contributor guide
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 the receiving parity-parts GET code discussed in PR #3497 and trace the loops that decide when redundant parts must be downloaded. Verify that the necessary download path no longer starts an unnecessary goroutine while preserving the existing GET behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100