[SERVER-12130] Document which device does mongoperf test Created: 16/Dec/13  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: Bug Priority: Minor - P4
Reporter: Andre Spiegel Assignee: Daniel Pasette (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

The mongoperf utility does not seem to have a way to choose which device to measure. It always seems to use the first device in the fstab.

If there is such an option, it needs to be documented. If there isn't, it needs to be added (and documented).



 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 TOOLS-1103 to be informed of updates as we weigh its priority against other projects that our Tools team are working on.

Comment by Scott Hernandez (Inactive) [ 16/Dec/13 ]

It creates a file in the current directory, not from a device in fstab... https://github.com/mongodb/mongo/blob/master/src/mongo/client/examples/mongoperf.cpp#L156

Please convert this to document that and it can be left up to the user to run it in the "correct" directory once help tells them that.

Generated at Thu Feb 08 03:27:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.