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.
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.
Data search functions
As you develop your HCL Link maps to search through data, you should consider the input format and the requirements for the output. Based upon those considerations, you can make your decision on which search function to use to for optimum performance results.

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.
      - Data search functions
        As you develop your HCL Link maps to search through data, you should consider the input format and the requirements for the output. Based upon those considerations, you can make your decision on which search function to use to for optimum performance results.
      - Search functions reference
        This documentation contains quantitative comparisons of the data search functions. It presents results of comparing the LOOKUP() against the SEARCHUP() or SEARCHDOWN() functions.
    - Routing
    - Map Profiler (dtxprof)
    - Page Setting Assistant for Maps (dtxpage)
- Glossary
  Performance related terms and definitions.

Data search functions

As you develop your HCL Link maps to search through data, you should consider the input format and the requirements for the output. Based upon those considerations, you can make your decision on which search function to use to for optimum performance results.

The following table lists search usage scenarios with the recommended function that should give you the best performance results.

Usage

Search Function Recommendation

Single output data item is the expected result and the input data cannot be sorted.

LOOKUP()

Multiple output data items are expected result.

EXTRACT()

The set of items to be searched is or can be sorted.

SEARCHUP() or SEARCHDOWN()

Same data type is being referenced (Positional Indexing).

In cases where CHOOSE() consistently references the same type, execution performance can exceed SEARCHUP() and SEARCHDOWN().

CHOOSE()