[SERVER-6332] mongoperf should be able to re-use existing data file Created: 06/Jul/12 Updated: 15/Mar/16 Resolved: 15/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jared Rosoff | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When mongoperf starts up, it deletes the existing tmpfile and creates a new one, even if the existing one is the right size. it would speed up testing if we could tell it to re-use the existing file on subsequent tests with the same fileSizeMB option. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 15/Mar/16 ] |
|
Apologies for the delay in responding on this issue, but we've decided not to proceed with any further enhancements to mongoperf in its current form - as such we're closing this as Won't Fix. We aren't moving the existing code or removing the binary, but any changes going forward would almost certainly involve first moving the existing functionality to a newly written tool. We made a similar decision with our other tools in 3.0.0 and have been very happy with the results. We don't have a specific timeline for this work, but you can vote on and add yourself as a watcher to |
| Comment by Zhehao Mao [ 26/Jul/12 ] |
|
Code review url: http://codereview.10gen.com/8190047 |
| Comment by Zhehao Mao [ 26/Jul/12 ] |
|
Can we keep the same file if the size for the current test is smaller than the size of the existing file? I don't think this would affect the test. |