[SERVER-24330] Find optimal configurations to concurrent fuzzing tasks Created: 31/May/16 Updated: 11/Jul/16 Resolved: 01/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.3.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Isabella Siu (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | TIG 17 (07/15/16) |
| Participants: |
| Description |
|
We should do some profiling to understand the resource requirements of concurrent fuzzer tasks to determine the best number of clients, the length of each test file and the number of test files. |
| Comments |
| Comment by Isabella Siu (Inactive) [ 01/Jul/16 ] |
|
The concurrent fuzzer is set to run with 10 clients and 75 test files and took between an hour and an hour and a half to run in the patch builds. |