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 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.
WorkSpace in Memory option
The WorkSpace in Memory option can be a viable choice for reducing I/O usage during transformation if enough memory is available. With a smaller input data file, the transformation engine can attempt to process the work file entirely in memory.

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.
    - 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.
      - Paging and I/O usage
        Paging controls the amount of data available to the transformation portion of the map execution at any time. If a map rule requires a piece of data that is not in memory, the paging subsystem will fetch the appropriate data from disk. This can impact existing data in memory; if there are no unused pages, an existing page is swapped out of memory.
      - Scenario: configure paging by input file size
        The following test scenario was created to demonstrate how the input size might require a larger information window or page setting, so it does not impact performance.
      - Configuring optimal page subsystem settings
        The settings for the paging subsystem in HCL Link can determine whether a transformation process runs bound by I/O bandwidth or by CPU capacity. These settings can impact system performance.
      - WorkSpace in Memory option
        The WorkSpace in Memory option can be a viable choice for reducing I/O usage during transformation if enough memory is available. With a smaller input data file, the transformation engine can attempt to process the work file entirely in memory.
  - 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.

WorkSpace in Memory option

The WorkSpace in Memory option can be a viable choice for reducing I/O usage during transformation if enough memory is available. With a smaller input data file, the transformation engine can attempt to process the work file entirely in memory.

Using this option:

Significantly reduces the number of I/O requests issued across the execution.
Produces optimal performance benefits when the work files do not exceed available physical memory. For more information about determining work file size, see the Reusing Work Files
When producing work files that exceed the amount of available physical memory, will cause operating system level-memory management to simulate additional memory with disk storage. This will ultimately degrade performance.