cubefs
[Enhancement]: Goroutine Pool Refactoring
-
Description:CubeFS is a new generation cloud-native open source storage system.The current system, based on a Golang framework, tracks the number of goroutines but frequently experiences goroutine leaks. There is no clear insight into which processes are utilizing the most goroutines, nor is there any timeout setting or quantitative management for certain goroutines. Overall, there is a lack of statistical output and metrics reporting. This functionality could be integrated into the util module and made available for use by various subsystems.
-
Recommended Skills: Go, basic familiarity with storage system
-
Expected Outcome:
- Enable comprehensive goroutine management
- Refactoring the current system's main processes with a goroutine pool implementation.
-
Expected project size: small (~90 hour projects)
Why is this needed?
No response
Anything else?
No response
Hi CubeFS team,
I'm interested in working on the "Goroutine Pool Refactoring" task from this list. I have recently worked on building a distributed file storage system in Golang, and I'm currently taking a parallel systems class this semester, which has given me solid experience with parallel computing concepts. I've been exploring Golang's goroutines in depth and would like to apply this knowledge to improve CubeFS.
I'm particularly interested in understanding:
What specific pain points exist with the current goroutine pool implementation The performance metrics or improvements you're hoping to achieve with the refactoring Any specific architectural approaches you'd prefer to see in the solution I'd appreciate any guidance from the assigned mentors (@Victor1319 and @leonrayang ) on getting started with this task, including pointers to the relevant sections of the codebase that utilize goroutine pools.
I'm excited about the opportunity to contribute to a CNCF project like CubeFS and am ready to dedicate time to this effort.
Thank you! AnishMulay
