[SERVER-35726] Enhance benchRun to not only take multiple ops, but also specify number of threads per op Created: 21/Jun/18 Updated: 06/Dec/22 Resolved: 05/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | tig-benchrun | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Tooling & Methods
|
||||
| Participants: | |||||
| Description |
|
I want to run two workloads in parallel, one doing reads and one doing writes, with a different number of threads doing each op. The best I can do is start two workloads via benchStart, sequentially, and then wait X seconds, and then call benchFinish sequentially. This hack is not very scientific, as launching a large number of threads can take a while and one workload is starting before the other. |
| Comments |
| Comment by David Daly [ 12/Jul/18 ] |
|
Yep – done. |
| Comment by Dianna Hohensee (Inactive) [ 12/Jul/18 ] |
|
david.daly could you keep this open, in the epic, until it gets addressed? It's unclear what PM-966 will specifically enable at this point, so it'd be nice to confirm that a solution exists before resolving. |
| Comment by David Daly [ 12/Jul/18 ] |
|
We're going to solve this a different way. |