[GODRIVER-477] benchmark max execution timeout counts setup time. Created: 22/Jun/18  Updated: 28/Oct/23  Resolved: 25/Jun/18

Status: Closed
Project: Go Driver
Component/s: Performance, Testing
Affects Version/s: None
Fix Version/s: 0.0.8

Type: Bug Priority: Major - P3
Reporter: Sam Kleinman (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

in the current harness we set a timeout on a context that we pass to the benchmark. We run the case for five minutes or 100 iterations (each operation has its own internal number of iterations, as well.)

The larger overarching timeout that we hit includes both setup code and actual execution time. As a result, we could run slightly fewer iterations than needed because the setup time counts towards the timeout.



 Comments   
Comment by Githook User [ 25/Jun/18 ]

Author:

{'username': 'tychoish', 'name': 'tycho garen', 'email': 'garen@tychoish.com'}

Message: GODRIVER-477: fix measurement error and resource useage

Change-Id: I73796712e2346f3cf52c1ecbca401bfeffc7532e
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/545effea171428c3e129274032cedbf9beb0e724

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