alluxio icon indicating copy to clipboard operation
alluxio copied to clipboard

Running Mixed Workloads in StressMasterBench

Open shuaiwuyue opened this issue 1 year ago • 1 comments

What changes are proposed in this pull request?

Currently, we can only execute a single workload in StressMasterBench, e.g., CreateFile. But in real world, workload are very complex which contains a large number of read and write requests . In this PR,I made a big change to StressMasterBench to support mixed workloads.

  1. Many new parameters have been added to StressMasterBench and old parameters have been given new meanings to help you more accurately describe the workload you want.
  2. Many new operations are added such as CURUD(Create->Update->Read->Update->Delete, for consistency test), CreateDeleteFile and UpdateFileMode.
  3. More running mode are proposed in BenchThread.
  4. Discard fixed count parameter and some logic about it.
  5. Discard masterMaxThroughput.
  6. Partially modified the format of the result.

Why are the changes needed?

Does this PR introduce any user facing changes?

Yes, the parameters of StressMasterBench have changed a lot and the format of StressMasterBench results is also different from the original one.

shuaiwuyue avatar Jul 27 '22 09:07 shuaiwuyue

Automated checks report:

  • Commits associated with Github account: PASS
  • PR title follows the conventions: FAIL
    • The title of the PR does not pass all the checks. Please fix the following issues:
      • First word of title ("Running") is not an imperative verb. Please use one of the valid words

Some checks failed. Please fix the reported issues and reply 'alluxio-bot, check this please' to re-run checks.

alluxio-bot avatar Jul 27 '22 10:07 alluxio-bot

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Feb 01 '23 15:02 github-actions[bot]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jun 16 '23 15:06 github-actions[bot]