golang methods that will yield goroutines

Issue

As far as I can understand, goroutines will block other goroutines from running if they are too busy. For me, this means that the performance and responsiveness of my application will probably depend on me knowing which library methods that will yield control over to other goroutines (e.g. typically Read() and Write())

Is there any way I can know exactly how different library methods will yield control over to other goroutines i.e. not actually block?

Is there any way I can implement a new method that calls third party code (including a async Win32 API like findnextchangenotification that relies on waitforsingleobject or waitformultipleobjects) and behaves “nice” with the Go scheduler? In this particular example, the syscall will signal once finished and I need to wait until it is finished withot exhausting all other goroutines.

Is there perhaps another “best practice” for how to deal with third party blocking operations in Go so that they don’t exhaust the other goroutines?

I assume that the Go runtime perhaps have some sort of IO-loop internally running on a background thread in order to “suspend” blocking goroutine operations until they finished with IO. If this is indeed the case, then I guess it could be useful to be able to build upon this for new blocking operations.

Solution

Go’s scheduler will suspend goroutines that are waiting for a syscall and wake them when the syscall has completed, giving you a synchronous API to deal with asynchronous calls.

Read more about how the scheduler works.

There is, however – no exact way of determining which goroutine will be awoken after another or yielding control from one goroutine directly to another – that’s the scheduler’s job.

Your concern is a solved problem in Go and you don’t have to worry about it – code away!

Edit:

To further clarify; you are not supposed to code to conform to (or make better use of) Go’s scheduler’s semantics — rather the other way around. There might be some code-tricks that can get you slight performance increase today but the scheduler can and will change in any future Go release — making your code optimizations useless or even work against you.

Answered By – thwd

Answer Checked By – Mary Flores (GoLangFix Volunteer)

Leave a Reply

Your email address will not be published.