Repository navigation
bench: compare Lua-CSharp, MoonSharp and NuLua on .NET 10 - #386
Merged
Merged
Conversation
akeit0
force-pushed
the
codex/pr-benchmark-comparison
branch
from
October 27, 2026 06:08
e330ef8 to
f54e526
Compare
akeit0
marked this pull request as ready for review
October 27, 2026 06:22
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.
Separate retained-chunk execution, source compilation and state startup, using shared Lua workloads with independent checksums. Add the NuLua.Lua52 0.1.0 backend alongside MoonSharp 2.0.0, and keep the older suites behind --legacy.
Initialize only the measured engine. Use bounded compilation batches because MoonSharp retains loaded sources, and add control-flow, identifier, plain-string and escaped-string compiler cases. Return LuaState resources from the legacy shared benchmark core. With no arguments, use BenchmarkDotNet's selector rather than starting a broad run.
Provide reproduction commands and explain the measurement boundaries, including the native-memory limitation. Generated run reports stay local. Validation: all 15 distinct checksums pass twice on three engines and both Lua-CSharp string modes; 12 selected BenchmarkDotNet measurements completed; Release build and CSharpier pass. CI runs checksum verification, not timing measurements.