Home
Performance recommendations
This documentation contains general performance tips and recommendations to improve performance.
General performance overview
This documentation describes what takes place during product execution and presents performance tips and recommendations regardless of the platform on which a specific HCL Link product is running.
Command Server operation overview
The first step in trying to achieve performance improvements running the Command Server in your environment is to understand Command Server operation.
Command Server work and data files
Depending on the conditions of the transformation, such as input data file size and processing complexity, work and data files can significantly affect performance.

Performance recommendations
This documentation contains general performance tips and recommendations to improve performance.
- General performance overview
  This documentation describes what takes place during product execution and presents performance tips and recommendations regardless of the platform on which a specific HCL Link product is running.
  - Performance measurement factors
    When analyzing how well an application has performed, there are potentially a large number of measurements that can be used to gauge workload efficiency in terms of the specific resources the application used.
  - Command Server operation overview
    The first step in trying to achieve performance improvements running the Command Server in your environment is to understand Command Server operation.
    - Command Server execution overview
      When you want to achieve performance improvements when running the Command Server in your environment, you must understand Command Server execution.
    - Command Server work and data files
      Depending on the conditions of the transformation, such as input data file size and processing complexity, work and data files can significantly affect performance.
      - Reusing work files
        Depending on the conditions of the transformation, such as input data file size and processing complexity, work and data files can significantly affect performance. When possible, reusing work files can produce measurable performance gains.
    - Command Server paging settings
      To minimize the memory footprint during transformation, HCL Link keeps only a subset of the work and data file information in memory at a given time.
  - Map performance and tuning best practices
    Many functions available to users for developing HCL Link maps are very powerful and can perform difficult and complicated tasks. Some functions may sacrifice performance for powerful capabilities, and it is important to understand the implications of these.
- Glossary
  Performance related terms and definitions.

Command Server work and data files

Depending on the conditions of the transformation, such as input data file size and processing complexity, work and data files can significantly affect performance.

Work and data files are the two major sources of information used in the transformation phase of map execution. Data files are the input data specified at execution time. Work files created during validation contain data about the input and output data sources.

The data types defined by the transformation's schema depend on the internal format of the data files and are ultimately determined by the business process. This internal format drives the validation phase. The storage characteristics of the data files also depend on the business process as well as the underlying operating system.

HCL Link offers a significant number of options for creating and using work files. Depending on the conditions of the transformation, such as input data file size and processing complexity, some of these options can significantly affect performance. Reusing Work Files, Paging and WorkSpace in Memory present the performance impact of these options.

The size requirements for work files ultimately depend on the number of type instances found in the input data file and generated in the output data file. The number of type instances found in both cases depends greatly on the type definitions. To save work file space, type instances are only recorded in the workspace if needed later in the transformation process.