VI Profiler shows high queue node times: is wire buffering the cause?

When profiling a producer‑consumer loop with LabVIEW’s VI Profiler, the Queue Enqueue and Dequeue nodes frequently dominate the CPU time column. This suggests a data‑transfer bottleneck, yet the profiler does not expose the underlying cause.

LabVIEW internally buffers wires to accommodate mismatched execution rates, but the activation threshold for this buffering is undocumented. The profiler’s time measurements may reflect the cost of this buffer management rather than the pure queue operation.

Because profiling overhead and target differences (Windows vs. Real‑Time) can influence the results, it is unclear whether the observed delay is a genuine bottleneck or an artifact of the hidden buffering logic.

What is the threshold that triggers internal wire buffering for queue nodes in LabVIEW? Can this threshold be configured or overridden through VI settings or runtime options? Does the threshold differ between LabVIEW 2020 and 2023, or between Windows and Real‑Time targets?