About: This article introduces the Share node, a Special node within Construct.
Location: Node panel
Table of Contents
Feature Overview
Splitting and Recombining Process Paths
The Share node is useful for splitting job processes into multiple streams that will later be recombined.
The Share node is not editable and does not require any configuration. It simply serves as buffer from the data source that multiple nodes can pull data from at once. If a user attempts to recombine streams without using a Share or Cache node at the point of the split, a Node Reentrancy error will occur.
Share Node vs. Cache Node
A Cache node can also be used to accomplish the same purpose. Both the Cache and Share nodes store data so it can be reused later, but they load data differently:
- Cache node: Loads and stores the entire dataset up front before downstream nodes use it. This can improve performance when the same data will be accessed many times, since all rows are already available in memory.
- Share node: Loads and stores rows only as they are needed by downstream processing. Instead of caching everything immediately, it builds its cache incrementally during execution. This can reduce upfront memory usage and startup time when only part of the dataset is needed.
Comments
0 comments
Article is closed for comments.