Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: 9.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- qo-triage-week

Assigned Teams:

Query Optimization
Operating System:
ALL
Steps To Reproduce:
Hide

Run Synthetic benchmarks with

"internalMeasureQueryExecutionTimeInNanoseconds": true
Show
Run Synthetic benchmarks with "internalMeasureQueryExecutionTimeInNanoseconds" : true
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

While developing https://github.com/10gen/dsi/pull/4315/ It was observed that there's a 200ms regression per query when using optimizationTimeNanos compared to using optimizationTimeMillis,

and was confirmed by running the same query set with and without Nano precision in a 3-time run patch at: https://performance-analyzer.server-tig.prod.corp.mongodb.com/perf-analyzer-viz/?comparison_id=69b82f4ea9505d426a53802e&selected_tab=scatter-plots&measurement_filter=AverageLatency&measurement_filter=OperationThroughput&percent_filter=0%7C%7C100&z_filter=0%7C%7C10&filter_type=Default