[SERVER-15977] Provide #ADD semantics to benchRun Created: 05/Nov/14  Updated: 06/Dec/22  Resolved: 11/May/20

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: 2.7.8
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Alvin Richards (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: 28qa, benchRun, benchrun-intern, community-team, tig-benchrun
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9573 Docs for SERVER-15977: Provide #ADD s... Closed
Duplicate
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

h2: Enhancement

Want to the ability to add number in order to create a range, for example

{_id: {$gt: <RND_NUM>, $lt: <RND_NUM>+50}}

This could look something like

{ op: "let", target: "x", value: {"#RAND_INT": [0,50] }},
{ op: "find", query: { _id : { $gt : { "#VARIABLE" : "x" }, 
                                          $lt : { "#ADD" : [{#VARIABLE: "x"},50 } } } }



 Comments   
Comment by Ryan Timmons [ 11/May/20 ]

Closing as wont-fix to indicate that there is currently no intention of doing this. New performance workloads are advised to be written in genny rather than benchRun. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue.

Comment by Chung-yen Chang [ 02/Jun/15 ]

This is a nice-to-have feature and will allow us flexibility in creating workloads using the benchRun framework. I am not sure what fix version to put this in for though. For now, I am putting 3.3 required and we can consider moving it depending on how our plates look like.

Generated at Thu Feb 08 03:39:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.