-
Notifications
You must be signed in to change notification settings - Fork 62
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
Performance #417
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jco has prioritised correctness over performance. As adoption grows, we will need to investigate performance more carefully, both for code generation and for host call overhead.
The first step here would be to obtain suitable performance benchmarks. The conformance test suite itself may be suitable for treating as a benchmark, but more dedicated benchmark components with predictable runtime performance would be beneficial here.
With benchmarks in place it would then be possible to explore:
There is potentially a lot of low-hanging fruit from a performance perspective, and it has not been a major priority yet. Hopefully this issue can point towards steps to take as users seek more investment here.
The text was updated successfully, but these errors were encountered: