Performance tuning - Data360_Analyze - 3 - 3.12

Data360 Analyze Server Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 Analyze
Version
3.12
Language
English
Product name
Data360 Analyze
Title
Data360 Analyze Server Help
Copyright
2023
First publish date
2016

The optimal configuration for your system depends on a number of factors, including the processing load on the machine (the number of records), and the mix and number of nodes that you are running.

The topics in this section describe some of the factors that impact the performance of your system and how to optimize your setup:

  • In-container execution - In-container execution is a feature that improves the performance of nodes when processing a moderate number of records. Nodes are processed in a "container" to reduce the latency in initializing node execution. This feature is switched on by default; if you want to disable it, see In-container execution.
  • Temporary file storage - If you need to save space in your temp directory, you can change the location of temporary files, see Changing the location of temporary files.
  • Java heap space - In general, we do not recommended changing the default Java heap space settings, however, should you need to make any adjustments, see Java heap space.
  • Thread limit configuration - By default, the thread limit is set to four. If you need to increase the limit, see Thread limit configuration.
  • Composite performance - You may notice a performance degradation if there is a run dependency between two composites that each have a large number of contained nodes. For a workaround, see Composite performance.