feat: benchmark against Luerl and C Lua#143
Merged
davydog187 merged 1 commit intomainfrom Feb 18, 2026
Merged
Conversation
This PR adds some benchmarks for getting an initial performance baseline. We have no implemented garbage collection or any performance optimizations yet, so there should be a lot of low-hanging fruit for improvement
c912093 to
ba63ed3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds some benchmarks for getting an initial performance baseline. We have no implemented garbage collection or any performance optimizations yet, so there should be a lot of low-hanging fruit for improvement. We are slower than Luerl across the board. Unclear if its related to our choice to build a register-based vm vs a stack-based vm yet.
Environment
Closures
Strange that eval would be signficantly faster here, it also seems that our closures are keeping around a lot more data
Fibonacci
Crazy amount of memory usage here, clearly recursion needs some optimization. Surprising that it is twice as slow
OOP
Strings
String Concatenation via table.concat (n=100)
String Formatting via string.format (n=100)
Tables
Table Build (n=500)
Table Sort (n=500)
Table Iterate/Sum (n=500)
Table Map + Reduce (n=500)