Why Is My Cgo Function So Much Slower Than My Equivalent Go Function?

Why Cgo's Performance Is Perplexingly Slow: Examining a Test Case

In an attempt to compare the execution times of Cgo and pure Go functions repeatedly, a tester encountered unexpected results. The Cgo function took significantly longer than the Golang function, leading to confusion and an exploration into the testing code.

The Testing Code in Question

The provided testing code below compares the execution times for Cgo and pure Go functions, each executed 100 million times:

import (
    "fmt"
    "time"
)

/*
#include <stdio.h>
#include <stdlib.h>
#include <string.h>

void show() {

}

*/
// #cgo LDFLAGS: -lstdc++
import "C"

//import "fmt"

func show() {

}

func main() {
    now := time.Now()
    for i := 0; i <h3 id="Unexpected-Results-and-Seeking-Answers">Unexpected Results and Seeking Answers</h3>
<p>The results obtained from the test code showed that invoking the C function was notably slower than the Go function. This led to the question of whether there was any flaw in the testing code itself.</p>
<h3 id="Diving-into-Cgo-s-Performance-Challenges">Diving into Cgo's Performance Challenges</h3>
<p>While the provided testing code is valid, the inherent performance limitations of Cgo contribute to the slower execution time observed for the Cgo function.</p>
<p>Calling C/C   code through Cgo incurs a relatively high overhead, and minimizing these CGo calls is generally recommended. In this particular scenario, moving the loop down to C instead of repeatedly invoking a CGo function from Go could potentially improve performance.</p>
<p>Additionally, CGo employs a separate thread setup for executing C code, making certain assumptions about the code's behavior. Some of these assumptions can lead to performance impacts:</p>
<ul>
<li>Goroutines in Go utilize relatively small stacks and handle stack growth dynamically.</li>
<li>CGo's thread handling can interfere with libpthread's thread local storage implementation.</li>
<li>Go's UNIX signal handler may disrupt traditional C or C   code.</li>
<li>Reusing OS threads for multiple Goroutines may have negative consequences if C code engages in blocking system calls or monopolizes the thread.</li>
</ul>
<h3 id="Conclusion">Conclusion</h3>
<p>CGo's role should be primarily seen as a gateway to interfacing with existing libraries, potentially with additional small C wrapper functions to reduce the number of calls made from Go. The expectation of C-like performance optimizations through CGo is generally not met, as there is already less of a performance gap between equivalent C and Go code.</p></string.h></stdlib.h></stdio.h>

The above is the detailed content of Why Is My Cgo Function So Much Slower Than My Equivalent Go Function?. For more information, please follow other related articles on the PHP Chinese website!