[SERVER-64419] create concurrent clients using locust Created: 10/Mar/22 Updated: 14/Mar/22 Resolved: 14/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Lamont Nelson | Assignee: | Rachita Dhawan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Clients should have coordination to start/stop |
| Comments |
| Comment by Lamont Nelson [ 14/Mar/22 ] |
|
rachita.dhawan We'll want the clients to perform our various types of data modification operations with parameterized percentages of each operation type. We'll want to be able to specify: For transactions, it probably makes sense to have a parameter for # documents updated per transaction, and we can set this to 1 if we need to have an apples to apples comparison to regular write operations. |