Sorting records has an impact on performance.
Keep the following factors in mind when attempting to assess the performance impact of the sorting feature:
Record sorting is a cached feature. That means that each dimension or property enabled for sorting increases the size of the dgraph process. The specific size of the increase is related to the number of records included in the data set. Therefore, only dimensions or properties that are specifically needed by an application for sorting should be configured as such. Sorting gets slower as paging gets deeper.
Because sorting is an indexed feature, each property enabled for sorting increases the size of both Dgidx process as well as the MDEX Engine process. (The specific size of the increase is related to the number of records included in the data set.) Therefore only properties that are specifically needed by an application for sorting should be configured as such.
In cases where the precomputed sort is rarely or never used (such as when the number of search results is typically small), the memory can be saved.
