[SERVER-50518] Improve slim_oplog_test.js to assert query performance Created: 25/Aug/20  Updated: 27/Oct/23  Resolved: 05/Jun/21

Status: Closed
Project: Core Server
Component/s: Querying, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-49890 Create local.system.resharding.slimOp... Closed
is related to SERVER-57478 Remove code related to local.system.r... Closed
is related to SERVER-36186 Ignore value of oplogReplay find comm... Closed
Assigned Teams:
Sharding NYC
Participants:
Story Points: 1

 Description   

SERVER-49890 hoped to verify that pipelining the oplog into a graphLookup on the local.system.resharding.slimOplogForGraphLookup view used the oplog hack for efficient lookup. However, the (amateur) observation is that while the code is performant as expected, $graphLookup does not integrate with explain. The work done by $graphLookup is allegedly completely unreported.



 Comments   
Comment by Max Hirschhorn [ 05/Jun/21 ]

The local.system.resharding.slimOplogForGraphLookup view is no longer used by resharding (SERVER-57303). slim_oplog_test.js shall be removed by SERVER-57478.

Comment by Max Hirschhorn [ 26/Aug/20 ]

One thought would be to write a genny workload which runs a $graphLookup pipeline on a view on the oplog. I'd vote to only run it on the 1-Node ReplSet Linux inMemory build variant in the /performance Evergreen project and not run it at all in sys-perf.

Generated at Thu Feb 08 05:22:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.