benchmark_data(3)
π benchmark_data(3) β a whole vibe check for ur benchmarks
okay bestie so this one lives in the Arcan Lua API, and it's literally the page for benchmark_data(3). Yeah. That's the name. Short and iconic, we love that for her π
β¨ NAME β¨
benchmark_data β retrieve gathered benchmarking values. that's it. that's the whole thing. she collects the numbers ur benchmark run has been quietly hoarding in the background and hands them to you π«Ά
πΈ SYNOPSIS πΈ
nticks, tickcosttbl, framecount, frametimetbl, costcount, framecosttbl
benchmark_data()
so the way this works is she gives you six whole return values at once, no cap, and you gotta catch them all in order:
nticksβ the tick count, babe. how many ticks we're talking about π«tickcosttblβ the tick cost table. the receipts for what each tick cost you πΈframecountβ the frame count. how many frames happened, fr fr ποΈframetimetblβ the frame time table. the time each frame took, in table form obviously πΈcostcountβ the cost count. she's counting costs, that's her job β¨framecosttblβ the frame cost table. more cost data, more tables, we stay fed π
like, she takes zero arguments. none. not even one. you just call benchmark_data() and she delivers the whole goodie bag ππ
π SEE ALSO π
the rest of the benchmark girlies, obvi:
benchmark_enable(3)β go turn the thing on first, bestie, otherwise what are you even measuring πbenchmark_timestamp(3)β for those lil timestamp moments β±οΈ
and that's the whole page, short and sweet, main character energy only πβ¨ this cutie comes from system, dated October 2026 β mwah, stan, periodt ππ
π¦ where this page comes from
- nixos 26.05: arcan 0.7.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms