[Bug] Benchmark nodes duplicates variables

Hi,

I’ve noticed that variables are duplicated by the Benchmark start nodes. Please see attaches screenshots:
unnamed

2019-03-25%2012_55_13-bans2065%20-%20Remotedesktopverbindung

2019-03-25%2012_56_01-bans2065%20-%20Remotedesktopverbindung

Whilst I guess the first variable is being used it also adds uncertainty in terms of reliability in case a workflow does not behave as expected.

Kind regards
Mike

Hi Mike,

Again this is something which I think is common to all nested loops in KNIME, e.g.:

image

Has at Node11:
image

And at Node12:
image

I agree that the duplicate names, presumably with different values during subsequent executions, is confusing but I think that is again pretty much hard-wired into the KNIME framework.

I’m wondering though - is there a reason why you are nesting two benchmarking loops, one with and one without the memory monitoring?

Steve

Thanks for the head up. reason why I was using two benchmark nodes was just for testing purpose. I stumbled across the duplicated variables the first time and thought it’s related to the benchmark nodes. Thanks again for the clarification.

1 Like

Thanks!

Steve