# Non-cost-based optimizations

The optimizer makes some non-cost-based optimizations, which means that it does not consider them when determining the access path and join order. If all the conditions are right, it makes the optimizations after the access path and join order are determined.

- Non-cost-based sort avoidance (tuple filtering)
- The MIN() and MAX() optimizations

Parent topic: DML statements and performance
Related concepts
Performance and optimization
Locking and performance
Overriding the default optimizer behavior