The performance of these comparison operators is highly dependent on the following Mondrian property:
# Max number of constraints in a single 'IN' SQL clause. mondrian.rolap.maxConstraints=1000
Under ideal conditions, the join between the numeric level and other report levels is done in the database so that only tuples with data are processed in Mondrian. This can only occur if, after applying the comparison operator, the number of members is less than the maxConstraints setting.