-
Notifications
You must be signed in to change notification settings - Fork 62
FIO Job File support #300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIO Job File support #300
Conversation
…ch uses a jobfile.
… a job file at runtime.
|
Could we include unit test for the fio job file parsing? |
I have added some unit tests now. |
|
The FioExecutor currently appends --ioengine & --filename to the command for the command line approach. I think it would make sense to keep the same in the job file approach, so I think we should expect the template job file that is provided to exclude the ioengine & file path parameters. EDIT: I was able to confirm again that if a parameter is provided in both the command line & the job file, then the value provided in the job file will take precedence. So it should not break if the parameter is provided in both. |
src/VirtualClient/VirtualClient.Main/profiles/PERF-IO-FIO-OLTP.json
Outdated
Show resolved
Hide resolved
…fill and one for operations.
Adding Job File support to the FIOExecutor class. Created a profile PERF-IO-FIO-OLTP to expose this feature. Tested on linux-x64, linux-arm64, windows-x64 VMs.