Page size mismatch - #69
Conversation
Case statement uses "pagesize" instead of "page_size" so neither version works. Put the underscore in the case statement
Option wasn't named for what it really means. We already have a max_file_size so using min_file_size which matches what iozone itself thinks the option means makes sense.
|
Warning Review limit reached
Next review available in: 41 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe CLI option and internal setting were renamed from ChangesMinimum file size option rename
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@iozone/iozone_run.sh`:
- Around line 683-684: Separate the manual-mode record-size value from
min_file_size in the throughput command around ioZone execution: add a dedicated
option/variable for the -r argument, while keeping min_file_size exclusively as
auto mode’s minimum file-size setting used by the existing -n and reporting
paths. Update the wrapper’s option parsing and documentation/help text so the
new record-size behavior is explicit.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 7d767ae9-f7c6-4896-be85-9d3a1e800ede
📒 Files selected for processing (2)
README.mdiozone/iozone_run.sh
Description
This resolves a failure in the "--page_size" option to validate due to the lack of the underscore in the option handling case statement. Since the intent of the option is to set the minimum file size for auto mode the ultimate resolution is to rename the option to min_file_size (which pairs well with the existing max_file_size)
Documentation is updated to reflect the changed option name
Before/After Comparison
Before: Using --page_size results in an option validation error in the option handling case statement due to a missing underscore
After: --page_size is replaced by the more accurately named --min_page_size and is handled properly
Clerical Stuff
This closes #67
JIRA: RPOPC-1242
Extract from raw results file using --min_page_size 4096
Extract from raw result allowing default to be used: