[ENH] Support RI-4 and RI-5 hybrid read workloads.

[rescrv]

No description provided.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[Sicheng-Pan]

Lgtm

[eculver]

For later, but I am a little hesisitant about hard-coding the 30/70 part here. In general, I feel like workloads should be parameterized so that these values can be driven by runtime config.

[rescrv]

The hard coded piece is the default pattern. You are free to shove json into the workload and make any pattern you wish.

[eculver]

I am ok with getting this merged so that we can start iterating. My primary concern is in my previous comment but is non-blocking.