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.
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.
Routing

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.
  - 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.
    - Data search performance best practices
      There are many ways to develop HCL Link maps that search through data. These different options provide varying balances between functionality and performance.
    - Routing
      - Data routing usage
      - Comparisons between the routing functions
    - Map Profiler (dtxprof)
    - Page Setting Assistant for Maps (dtxpage)
- Glossary
  Performance related terms and definitions.

Routing

Routing is the splitting of output to separate files based on the data values. This is a common operation in many HCL Link mapping procedures. This documentation discusses differences between the PUT() and RUN() functions when used to route data. The behavior of each is broader than simply routing, and neither function is an exact replacement for the other.

The various functions available to the map developer to do data routing are:

PUT()
RUN()

For both the PUT() and RUN() functions, the best performance for routing style maps is generally obtained by mapping the largest available group object.

The following table contains the two functions available to the map developer to do data routing.


Function	Use	Advantage	Disadvantage
`PUT()`	Routes an output item to an adapter.	Overhead is less than using `RUN()`.	I/O and CPU overhead from repeated opening and closing of routing targets can be great for large maps.
`RUN()`	Allows a map that is currently running to execute another map.	Is versatile. Using a second map to process output allows for a great deal of flexibility in output generation.	Overhead is much greater than using `PUT()`. I/O and CPU overhead from repeated opening and closing of routing targets can be great for large maps.