Open gopherbot opened 1 month ago
This causes a dramatic drop in C -> Go call performance under some circumstances.
Hi @aclements, I wanted to work, this can be a potential workaround.
// Workaround: Use `runtime.LockOSThread()` to minimize thread switching overhead.
// This ensures the goroutine stays on the same OS thread during C -> Go calls.
runtime.LockOSThread()
defer runtime.UnlockOSThread()
Would this be viable? Feedback appreciated.
@Arup-Chauhan the problem has already been worked on, the changes should be in next go release and also backported to go1.23. In fact, we're on the backporting issue here. See #68587
Thankyou for the update @arl , I will try to contribute to some other issue then
We moved the NextMinor label to the parent tracking issue #68587, removing here.
@aclements requested issue #68587 to be considered for backport to the next 1.23 minor release.