-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
Fully Compatible
-
QO 2024-03-04
We currently always populate the cluster time and localNow time when constructing the ExpressionContext even if the variables are unreferenced in any expressions. This shows up in flamegraphs for fast running queries like ycsb.
- is related to
-
SERVER-82647 Avoid getting current VectorClock in Variables::generateRuntimeConstants
- Closed