Hi folks! I'm member of Node.js team and I'm conducting a research on our benchmark suite (https://github.com/nodejs/node/tree/main/benchmark).
In our benchmarks, we attempt to avoid the measured block from being eliminated by V8 dead-code elimination by making use of a state and checking the state after the benchmark run. Example: https://github.com/nodejs/node/blob/main/benchmark/blob/clone.js#L24 However, this is an assumption, we do not check if the measured block is being eliminated so, the benchmark result will be noop or we are measuring it correctly. I tried to run the benchmark with --trace-turbo and analyzing it with tools/turbolizer, but I couldn't find a way to identify which blocks were removed. Is there a way to do that? I understand that usually micro-benchmarks are far from reliable, but at the moment I don't see how we could make it more sophisticated and specific. Thanks in advance -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/4e060cb2-477c-4037-876a-bd2f5aab245fn%40googlegroups.com.
