使用gperf测了下, 发现signal_task占比好高, 是否可以像mutex那样, 只在必要的时候才进入系统调用
Open
- Dominant language
- C++
- Stars
- 17.6k
- Forks
- 4.1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 69
Description
[tmp.pdf](https://github.com/apache/brpc/files/12645457/tmp.pdf)
Contributor guide
Research direction
Start by reviewing the attached tmp.pdf and locating the signal_task and mutex paths in the brpc source. Compare when each path enters a system call and establish a benchmark or profile for the current signal_task overhead. Done means unnecessary system calls are avoided without changing the relevant behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100