Investigation and example workflow from that thread reveals that the benchmarking nodes can currently only report node timings when they are at the root level of a workflow. Embedding them in metanodes or components causes them to fail with an IndexOutOfBounds exception.
sroughley
commented
2 years ago
Reported vie forum at https://forum.knime.com/t/error-benchmark-nodes-fromindex-1-toindex-0-when-in-component/19062/4?u=vernalis
Investigation and example workflow from that thread reveals that the benchmarking nodes can currently only report node timings when they are at the root level of a workflow. Embedding them in metanodes or components causes them to fail with an
IndexOutOfBoundsexception.