[SERVER-34297] bench_test1.js should use write commands Created: 04/Apr/18 Updated: 24/Aug/23 Resolved: 24/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Declined | Votes: | 0 |
| Labels: | stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Tooling & Methods
|
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The updates sent by bench_test1.js should use write commands. This should ensure that we wait for acknowledgment before issuing the next command, so we will have at most two write operations executing on the server at once. This will avoid the issue where we can have many write operations stuck in retry loops on the server. |
| Comments |
| Comment by Robert Guo (Inactive) [ 27/Feb/20 ] |
|
We're moving away from benchrun in favor of Genny and Google Benchmark. |
| Comment by Spencer Brody (Inactive) [ 31/May/18 ] |
|
This does't actually seem replication related at all. max.hirschhorn, feel free to close this if you don't think it's worth doing. |