The scenario is when a server handling a large number of connections while the business logic is
very simple (that is, IO-bound not CPU bound), the switching of goroutines is expensive, and also unnecessary.
So, is there a goroutine schedule schema in which one goroutine runs until it traps into kernel mode.
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.