50cef32ae0
This adds the new vs target to measure the cost of host function calls. Notably, I can see that wazero is roughly 2x to 4x times faster than CGO-based runtimes in terms of host call boundary crossing. One implication here is that we can just focus on the native code generation rather than how to organize the Go function calls. For example, it's not prioritized to call Go functions directly from the native code. Signed-off-by: Takeshi Yoneda <takeshi@tetrate.io>
49 lines
1.3 KiB
Go
49 lines
1.3 KiB
Go
package vs
|
|
|
|
import (
|
|
_ "embed"
|
|
"testing"
|
|
|
|
"github.com/tetratelabs/wazero/internal/testing/require"
|
|
)
|
|
|
|
var (
|
|
//go:embed testdata/hostcall.wasm
|
|
hostCallWasm []byte
|
|
hostCallConfig *RuntimeConfig
|
|
hostCallFunction = "call_host_func"
|
|
hostCallParam = uint64(12345)
|
|
)
|
|
|
|
func init() {
|
|
hostCallConfig = &RuntimeConfig{
|
|
ModuleName: "hostcall",
|
|
ModuleWasm: hostCallWasm,
|
|
FuncNames: []string{hostCallFunction},
|
|
EnvFReturnValue: 0xffff,
|
|
}
|
|
}
|
|
|
|
func RunTestHostCall(t *testing.T, runtime func() Runtime) {
|
|
testCall(t, runtime, hostCallConfig, testHostCall)
|
|
}
|
|
|
|
func testHostCall(t *testing.T, m Module, instantiation, iteration int) {
|
|
res, err := m.CallI64_I64(testCtx, hostCallFunction, hostCallParam)
|
|
require.NoError(t, err, "instantiation[%d] iteration[%d] failed", instantiation, iteration)
|
|
require.Equal(t, hostCallConfig.EnvFReturnValue, res)
|
|
}
|
|
|
|
func RunTestBenchmarkHostCall_CompilerFastest(t *testing.T, vsRuntime Runtime) {
|
|
runTestBenchmark_Call_CompilerFastest(t, hostCallConfig, "HostCall_CrossBoundary", hostCall, vsRuntime)
|
|
}
|
|
|
|
func RunBenchmarkHostCall(b *testing.B, runtime func() Runtime) {
|
|
benchmark(b, runtime, hostCallConfig, hostCall)
|
|
}
|
|
|
|
func hostCall(m Module) error {
|
|
_, err := m.CallI64_I64(testCtx, hostCallFunction, hostCallParam)
|
|
return err
|
|
}
|