In the LargeIndexedIn workload, 15% of total CPU time is spent in isValidFor(), which validates that the index bounds are in the correct order relative to the scan and index direction (for example, the bounds [1,3] is valid for ascending index + forward traversal and descending index + backwards traversal). isValidFor() is invoked immediately after aligning the bounds to satisfy the proper direction, and only used to log and tassert if it fails.

Given the cost in a high-value workload, we should consider disabling this check in release builds.