Title: Benchmark harness: PUC Lua timings and LuaJIT trace/FNEW counters for generated code · Issue #172 · purescript-lua/purescript-lua · GitHub
Open Graph Title: Benchmark harness: PUC Lua timings and LuaJIT trace/FNEW counters for generated code · Issue #172 · purescript-lua/purescript-lua
X Title: Benchmark harness: PUC Lua timings and LuaJIT trace/FNEW counters for generated code · Issue #172 · purescript-lua/purescript-lua
Description: Problem The test suite checks the shape of generated code (structural goldens) and its semantics (eval goldens), but nothing measures performance. The upcoming optimization series (uncurrying #24, intrinsic inlining, inliner heuristics) ...
Open Graph Description: Problem The test suite checks the shape of generated code (structural goldens) and its semantics (eval goldens), but nothing measures performance. The upcoming optimization series (uncurrying #24, ...
X Description: Problem The test suite checks the shape of generated code (structural goldens) and its semantics (eval goldens), but nothing measures performance. The upcoming optimization series (uncurrying #24, ...
Opengraph URL: https://github.com/purescript-lua/purescript-lua/issues/172
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Benchmark harness: PUC Lua timings and LuaJIT trace/FNEW counters for generated code","articleBody":"## Problem\n\nThe test suite checks the shape of generated code (structural goldens) and its semantics (eval goldens), but nothing measures performance. The upcoming optimization series (uncurrying #24, intrinsic inlining, inliner heuristics) needs every change to defend its win with a number, and wins must not silently regress afterwards.\n\nMotivating measurements (PUC Lua 5.1.5 / LuaJIT 2.1, 2e7 iterations): a curried hot loop `acc = add(acc)(i)` runs 0.91 s under LuaJIT and 0.90 s with the JIT disabled via `-joff` — the JIT contributes nothing, because every trace recording aborts on `NYI: bytecode FNEW` (closure creation, executed on every partial application) and the loop start gets blacklisted. The uncurried equivalent compiles to a single trace and runs 0.017 s (54x). Driving the linked `Data.Array.foldl` with a curried step function reproduces this on real generated code: 0.99 s vs 0.012 s (85x), with the FFI fold loop itself blacklisted even though it is a plain `for` — the trace has to inline the curried callee.\n\n## Approach\n\nA `bench/` directory, separate from the test suite:\n\n1. Microbenchmarks of codegen patterns, timed under both PUC Lua and LuaJIT: curried application, dictionary-driven comparison (`greaterThanOrEq ordInt` vs native `>=`), constructor allocation + tag match, `M.\u003cfield>` access vs a local.\n2. Macrobenchmarks driving linked real modules: the Fibonacci golden, `Data.Array.foldl` over a large array, a monadic bind chain.\n3. Deterministic LuaJIT counters, suitable for CI: the number of `FNEW` bytecodes in `luajit -bl` output of linked artifacts, split into main-chunk (runs once at init) vs function-body (runs per call) occurrences, and abort/blacklist event counts from `luajit -jv` runs of the macrobenchmarks.\n\nWall-clock timings stay in a local script — too noisy for CI. The counters are deterministic, so they can run as a CI smoke check and record the trend as optimizations land.\n\nRequires adding `luajit` to the nix dev shell (currently only PUC Lua 5.1 is available there).\n\n## Prerequisites / Relations\n\nInfrastructure with no hard prerequisite — self-contained apart from adding `luajit` to the nix dev shell. It should land early in the perf series: every perf change (#178, #179, #24, #180, #181, #173, #174, #185) cites this harness to defend its win, and the closing-audit issue #187 reads the trend it records.\n\n## Verification / Measurement\n\nDone when the harness reproduces the baselines already recorded above on the current linked artifacts — curried application ~54x slower under LuaJIT, `Data.Array.foldl` ~85x, `FNEW` emitted on every partial application, the fold loop blacklisted — and the LuaJIT counters (main-chunk vs function-body `FNEW` counts; abort/blacklist counts from `-jv`) are byte-stable across runs so CI can assert on them. Wall-clock ratios come from the local script; CI gates on the deterministic counters.\n","author":{"url":"https://github.com/Unisay","@type":"Person","name":"Unisay"},"datePublished":"2026-07-06T09:07:35Z","url":"https://github.com/purescript-lua/purescript-lua/issues/172"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:daef6cec-c19b-d8d9-7944-49587a863e39 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | DC40:2AAD2E:7DB8F3:A9CBDE:6B00E04C |
| html-safe-nonce | a9105a3ef9a770fc4efdc123de285d8e420b75d5c2d9881f33dc8924538564c1 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEQzQwOjJBQUQyRTo3REI4RjM6QTlDQkRFOjZCMDBFMDRDIiwidmlzaXRvcl9pZCI6IjQwNTg4MDA2NDgzNDk2MDU5NjQiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | face5bf15f97c87b8157388e37fa1f46929a5ded30423cc7eebda95eda3230f1 |
| hovercard-subject-tag | issue:4817616001 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/purescript-lua/purescript-lua/172/issue_layout |
| twitter:image | https://opengraph.githubassets.com/2513f64e7b9d0e706bec4dc75ba63a31c2f1e7217c432e0c208cc1cac441f2d7/purescript-lua/purescript-lua/issues/172 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/2513f64e7b9d0e706bec4dc75ba63a31c2f1e7217c432e0c208cc1cac441f2d7/purescript-lua/purescript-lua/issues/172 |
| og:image:alt | Problem The test suite checks the shape of generated code (structural goldens) and its semantics (eval goldens), but nothing measures performance. The upcoming optimization series (uncurrying #24, ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Unisay |
| hostname | github.com |
| expected-hostname | github.com |
| None | 043c3f30fbcbe2c6c8e729e10cbbbc90c406546f9fbbb67c648d38f6b7d16daf |
| turbo-cache-control | no-preview |
| go-import | github.com/purescript-lua/purescript-lua git https://github.com/purescript-lua/purescript-lua.git |
| octolytics-dimension-user_id | 131581790 |
| octolytics-dimension-user_login | purescript-lua |
| octolytics-dimension-repository_id | 587200487 |
| octolytics-dimension-repository_nwo | purescript-lua/purescript-lua |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 587200487 |
| octolytics-dimension-repository_network_root_nwo | purescript-lua/purescript-lua |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 5425dc24e8bd8d6fca9641a12afc984825a43875 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width