Unofficial Content
  • This documentation is valid for:

Spanish Version

Performance Improvements

Scope

Product: GXplorer, GXquery

Introduction

Some changes have been introduced in the operation of queries specification and execution in order to improve the interaction with the end user, increasing the performance of these tasks. The most important point are:

  • Load at request of elements trees (measures, dimensions, queries), loading and showing only those element that the user needs at any moment.
  • Generated statements cache to perform queries execution and access to the associated KB in attributes metadatas, allowing not to calculate again statements already used.

Description

The following changes have been made aiming at obtaining a better interaction with the end user while specifying and executing queries. These changes generate important performance improvements.

Elements loading at request

In every dialog where element trees are shown (attributes, measures, dimensions and catalogued queries), these elements are loaded at request. I.e.: initially, only the first available element is loaded, and the remaining ones are loaded as the user expands the different folders.
There follows an example of how this new mechanism operates. A catalogued query is edited and only the first element levels are shown in an initial stage. The Customer folder and then the Country folder are expanded, which results in the loading at request of the detail of the attributes associated to the folder over which the logged user has rights. 

GXBI-Perf01

This generates important improvements in the interaction between the application and the end user while the queries are being specified.

Note: When using the Settings utility, the elements loading at request is not taken into account.

Generated Statements Cache Management

When working with attribute metadatas, a cache of generated statements and related attributes is automatically enabled to minimize the interaction time with the user while specifying the query to be solved. An elements cache is managed in two levels
:
  • On editing a query, adding or deleting elements to/from the specification, query-related elements are automatically calculated. Each time a query is validated, those elements related to a given specification are cached and reused in future executions.
  • Each time a query is executed, it is verified in the SQL statements cache. If there is already a statement matching this query, the statement is used; otherwise, the algorithms in charge of solving the statement are executed. Then, the cache entry is added and the query is executed. This cache has an important impact for already catalogued queries.
The cache is managed from the Settings utility, accessing the Cache section within the Settings section, as shown in the following figure:

GXBI-Perf02 

Considerations

  • The cache is automatically initialized when impacting the metadata.


Last update: February 2024 | © GeneXus. All rights reserved. GeneXus Powered by Globant