Using photon::semaphore on AWS EC2, `signal` latency is high.
Open
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 179
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 26
Description
Using photon::semaphore on AWS EC2, `signal` latency is high.
I have using `photon::semaphore` on AWS EC2. I found `signal` function may cost 300~600ms. I don't know what happens and why `signal` cost so long. I'm seeking assistance in understanding the cause and debugging strategies🙏.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported 300–600 ms `photon::semaphore` `signal` latency on AWS EC2 and inspect the semaphore signaling path. Use the reproduction to identify the cause and document debugging findings or a clearly scoped fix; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100