Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cgo / FFI performance #8

Open
mingue opened this issue Nov 3, 2022 · 1 comment
Open

Cgo / FFI performance #8

mingue opened this issue Nov 3, 2022 · 1 comment

Comments

@mingue
Copy link

mingue commented Nov 3, 2022

Go will be an amazing language for systems programming too, but there is a big performance penalty on interoperability as everything is a goroutine. If this issue is solved suddenly you will get exposed to a huge amount of libraries comatible with c without performance impact, quickly expanding the uses cases for go, ML, AI, Big Data, Graphics...

More info here: https://stackoverflow.com/questions/28272285/why-cgos-performance-is-so-slow-is-there-something-wrong-with-my-testing-code#28272990

@mingue mingue changed the title FFI performance Cgo / FFI performance Nov 3, 2022
@avivcarmis
Copy link
Contributor

The current idea behind goat is a compile time language (similar to the idea behind typescript if you're familiar with that), meaning that goat files are translated into go files and then executed by go runtime.
With this direction I'm not sure we could gain access to runtime aspects like goroutine implementation.
Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants