Queue Node
Sometimes Nash is too fast. As much as we’d like to make things go fast, some systems can’t handle the proverbial fire hose of data that Nash can blast out. In these cases, to ensure you’re not overwhelming your target systems, the Queue node is very useful.
The Queue node allows you to define the rate at which Nash sends records to a target.
There are two ways the Queue node accomplishes this: 1) Throttling and 2) Pausing.
Throttling
In the case below, you can see we’re throttling the data flow, setting the data flow to 1 record every 500 milliseconds.
As the Nash throttling prompt says below, throttling “Queues records wherever this node is placed in the flow and will release one record per the set number of milliseconds to continue processing.”
Pause
Again, as Nash says below, choosing the pause option “Will pause the current record’s processing for the set number of milliseconds wherever this node is placed in the flow.” This action allows a target system to pause long enough to “catch its breath.” The example below shows Nash enabling a 2000 ms (2 second) pause before sending more data.
