benchmark_tracedata(3)

💅 benchmark_tracedata(3) — Arcan Lua API

okay so bestie, this one lives in the Arcan Lua API section of your manuals (benchmark_tracedata(3) to its friends) and it's literally the "drop a lil datapoint in the tracebuffer" girlie. let's get into it 🎀

---

✨ NAME ✨

benchmark_tracedata — add a datapoint to the ongoing tracebuffer 🫶

---

🌸 SYNOPSIS 🌸

nil
benchmark_tracedata( string:subsystem, string:message )
benchmark_tracedata( string:subsystem, string:message, int:identifier=0,
int:quantity=1 )
benchmark_tracedata( string:subsystem, string:message, int:identifier=0,
int:quantity=1, int:trigger=TRACE_TRIGGER_ONESHOT )
benchmark_tracedata( string:subsystem, string:message, int:identifier=0,
int:quantity=1, int:trigger=TRACE_TRIGGER_ONESHOT,
int:level=TRACE_PATH_DEFAULT )
benchmark_tracedata( string:subsystem, string:message, int:identifier=0,
int:quantity=1, int:trigger=TRACE_TRIGGER_ONESHOT,
int:level=TRACE_PATH_DEFAULT )

no cap, she returns nil — this is a side-effects-only icon, she adds the datapoint and dips 💨 and yes the last two signatures are identical, that's just how the page is, we don't ask questions bestie 😭💀

---

💖 DESCRIPTION 💖

so what she does is: this function adds a datapoint to the ongoing tracebuffer. that's the whole vibe. ✨

for how the buffer and its reporting function get used and configured, go look at benchmark_enable — that's the main character of this story, this is her supporting role. 👑

the possible arguments are:

• 'subsystem' — caller defined 🌸
• 'message' — caller defined (yes you get to name your own message, slay) 💅
• object identifier — caller defined 🦋
• quantity indicator — also a thing you pass in 🍓
• trigger — picked from the set of TRACE_TRIGGER_ONESHOT, TRACE_TRIGGER_ENTER, TRACE_TRIGGER_EXIT 🔥
• performance path — one of TRACE_PATH_DEFAULT, TRACE_PATH_SLOW, TRACE_PATH_WARNING, TRACE_PATH_ERROR, TRACE_PATH_FAST 🌈

and the defaults, since we're being specific: int:identifier=0, int:quantity=1, int:trigger=TRACE_TRIGGER_ONESHOT, int:level=TRACE_PATH_DEFAULT. periodt. don't come for me, that's literally what the page says 💜

---

🧚 EXAMPLE 🧚

okay this is the fun part, look at her go:

function benchmark_tracedata0()
      benchmark_enable(1,
      function(res)
            for k,v in ipairs(res[1]) do
                  print(k, v);
            end
      end)
      benchmark_tracedata("test", "hi", 10, TRACE_TRIGGER_ONESHOT, TRACE_PATH_DEFAULT)
end

so you benchmark_enable with a reporting function that loops over res[1] with ipairs and prints k, v, then you fire off one benchmark_tracedata("test", "hi", 10, TRACE_TRIGGER_ONESHOT, TRACE_PATH_DEFAULT). iconic behaviour honestly 🎀

---

🦋 SEE ALSO 🦋

• benchmark_enable(3) — go read her, she's the one who actually configures all this 🫶

---

lowkey reminder bestie: every value up there is exact — the TRACE_TRIGGER_* set, the TRACE_PATH_* set, and those defaults. copy-paste them, don't freestyle them 🙈

---

⭐ that's the whole page! brought to you by the system manual, October 2026 release, benchmark_tracedata(3) — mwah, go trace some data, you got this 💖✨🌸