FAQ
Adam, if you have a particular benchmark in mind, we'd love to see it.
It's much easier to reason about these things in the concrete instead of
the abstract.

On Wed, Mar 23, 2016 at 2:45 PM, minux wrote:

The overhead of cgo calls are definitely not because of switching stacks,
because it's just switching a few registers. If switching stack is the main
bottleneck, then switching goroutinea will see similar slowness.

The overhead comes from scheduler coordination (goroutines in cgo calls
are not counted towards GOMAXPROCS)

--
You received this message because you are subscribed to the Google Groups
"golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 13 | next ›
Discussion Overview
groupgolang-dev @
categoriesgo
postedMar 23, '16 at 9:32p
activeMar 24, '16 at 8:34a
posts13
users7
websitegolang.org

People

Translate

site design / logo © 2021 Grokbase