Home > Workflow > Working with Nodes > Setting Parallel Processing... > Edit Node Performance Settings
In the Edit Selected Node Settings, you can set Parallel Processing settings and In-Memory settings for one or all nodes in the workflow.
Select Parallel Query On to set parallel processing for the node. If you specify parallel processing for a node type, then the query generated by the node may not run in parallel.
System Determined: This is the default degree of parallelism.
Degree Value: To specify a value for degree of parallelism, select this option and choose a value by clicking the arrows. The default value is 1. The specified value is displayed in the Degree of Parallel column for the node type in the Performance Options and Edit Selected Node Settings dialog boxes.
Select In-Memory Columnar option to set the compression method and priority level for the selected node. The selected settings are displayed in the In-Memory Settings option in the Performance Options dialog box.
Compression Method: Allows you to set a compression method for the data.
|
Note: The higher you set the Compression method, the lower will be the performance of the query. |
None: In this method, the data is not compressed.
Low: This method results in the best query performance.
Medium: This method optimizes the data for DML operations and compresses the IM column
High: This method results in excellent query performance.
Higher: This method results in good query performance.
Highest: This method results in a fair query performance.
Priority Level: The priority level that you set here determines when the data of the database object is populated in the IM column store.
None: This is the default setting when priority is not included in the INMEMORY clause.
Low: Populates the data before database objects with the priority level NONE and after priority levels: MEDIUM, HIGH or HIGHEST.
Medium: Populates the data before database objects with the priority levels: NONE or LOW, and after priority levels: HIGH or HIGHEST.
High: Populates the data before database objects with the priority levels: NONE, LOW, or MEDIUM and after priority level: HIGHEST.
Highest: Populates the data before database objects with the priority levels: NONE, LOW, MEDIUM, or HIGH.