hxtelemetry
hxtelemetry copied to clipboard
Report telemetry overhead
If these pile up, it's bad news. Probably should report this (in case AUT is slow/stutters.)
Notes: Related to the finalizer / mark/sweep mechanism -- I'm working on quantifying the telemetry overhead in the GC, so I can report what's "real GC time" and what's "telemetry overhead GC time". Perhaps I should/could subtract GC time (which is invoked under the hood in hxcpp) from the stack that's active/paused while it runs...
Also, mentioned above, how about overhead as # frames waiting to be dumped? Meh, not sure it's as useful.