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
Data routing usage

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.

Data routing usage

As you develop your HCL Link maps to route input data and create output, you consider the format of the input and the requirements for the output. Based upon those considerations, you can make your decision on which routing function to use to derive optimum performance results. The following table lists the routing usage with the recommended function that should give you the best performance results.

Usage: Routing Function Recommendation
Avoid using additional maps to route data. Instead, try to use PUT() with the appropriate adapter whenever possible.: PUT
Additional processing with a secondary map is required.: RUN

As stated previously, the functionality of PUT() and the functionality of RUN() differ significantly. Because RUN()enables the map to execute a secondary map, there might be many routing situations where PUT() might not be a feasible choice. In cases where PUT() can be used, usually better performance results.