Run-time performance of the MDEX Engine is directly related to the number of refinement dimension values being computed for display.

If any refinement dimension values are being computed by the MDEX Engine but not being displayed by the application, stricter use of the Ne parameter is recommended. Obviously, dimensions containing large numbers of refinements also affect performance.

The worst-case scenario for run-time performance is having a data set with a large number of dimensions, each dimension containing a large number of refinement dimension values, and setting the ENEQuery.setNavAllRefinements() method (Java) or ENEQuery.NavAllRefinements property (.NET) to true. This would create a page with an overwhelming number of refinement choices for the user.