On Tuesday, 22 November 2016 18:51:46 UTC+8, Dave Cheney wrote: > > Why do you want to use LockOSthread, you've proved it has a significant > performance cost for your application.
*Cgo* is the answer..... (Actually I want to use a C library(which needs LockOSthread to reach local constant thread execution model) through Cgo in the Go application.And one of the biggest benefits of Go is the Channel's event notification mechanism which is on the user space and powerful.It could be used to create a sync & nonblock application easily.) Is this a expected performance penalty when we use channel with LockOSthread?(Maybe due to a design tradeoff or anything) (: Just want to figure it out and be sure the exclusion of the probability of some bugs maybe hidden on this test codes here :) -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
