Skip to content

docs: rewrite README to match wrapper documentation standard#60

Open
sayalibhavsar wants to merge 1 commit into
masterfrom
docs/rewrite-readme
Open

docs: rewrite README to match wrapper documentation standard#60
sayalibhavsar wants to merge 1 commit into
masterfrom
docs/rewrite-readme

Conversation

@sayalibhavsar

@sayalibhavsar sayalibhavsar commented Jun 15, 2026

Copy link
Copy Markdown

Summary

  • Comprehensive rewrite of the specjbb-wrapper README modeled after the autohpl-wrapper documentation structure
  • All content derived from specjbb-wrapper source code — no invented functionality
  • Removes stale pbench references from the original documentation
  • Adds all general_setup options (--debug, --no_pkg_install, --no_system_packages, --no_pip_packages, --run_label, --test_tools_release, --verify_skip, --json_skip)

New sections added

  • Command-Line Options: complete listing of both specjbb-specific and general_setup options
  • What the Script Does: 11-step workflow breakdown
  • Dependencies: per-OS Java package matrix for all supported versions (11, 17, 21, 23, 24, 25)
  • The SPECjbb2005 Benchmark: key parameters, performance metric (BOPs), multi-JVM architecture
  • Output Files: file listing and results schema table
  • Examples: 11 usage examples covering common scenarios
  • How Warehouse Sizing Works: auto-sizing logic with formulas
  • How JVM Stack Sizing Works: heap calculation explanation
  • Return Codes: error code reference
  • Notes: licensed workload, architecture support, Java version matrix, NUMA considerations, reduce_jbb.sh utility, performance tips, troubleshooting

Solves #59
Relates to JIRA: RPOPC-937

@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@sayalibhavsar, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 4 minutes and 18 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 98fb87a1-146c-45ed-9db9-d74bde65fa83

📥 Commits

Reviewing files that changed from the base of the PR and between 17f6eb5 and b309f2a.

📒 Files selected for processing (1)
  • README.md
📝 Walkthrough

Walkthrough

README.md is substantially rewritten from a minimal description into comprehensive documentation. It adds a full CLI options reference, an 11-step workflow walkthrough, dependency and Java package requirements, benchmark background, output file descriptions, multiple example invocations, warehouse and JVM sizing logic, return codes, and expanded notes with troubleshooting guidance.

Changes

SPECjbb2005 Wrapper README Rewrite

Layer / File(s) Summary
Header, description, and CLI options
README.md
Replaces the old short wrapper description with a new title, overview, and a comprehensive command-line options list covering SPECjbb-specific and general test_tools flags.
Workflow steps and dependencies
README.md
Adds an 11-step structured walkthrough of what specjbb_run does, a dependencies section for the licensed kit location and required base packages, per-Java-version OS package mappings, copy/clone/run instructions, benchmark background concepts, output file enumeration, and a results-schema constraints table.
Examples section
README.md
Adds a dedicated Examples section replacing the previous sparse usage snippet, covering defaults, Java version selection, NUMA-aware JVM counts, NUMA pinning, explicit JVM count, warehouse range, iterations, regression mode, PCP monitoring, and kit specification.
Sizing logic, return codes, and notes
README.md
Introduces warehouse sizing rules (end/start/increment, multi-JVM division, regression behavior) and JVM stack/heap sizing logic; adds return codes documentation; expands Notes and Troubleshooting with licensing, architecture/JVM support, NUMA and performance tips, reduce_jbb.sh utility description, and updated troubleshooting bullets.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly and concisely describes the main change: a comprehensive rewrite of the README to match an established documentation standard.
Description check ✅ Passed The PR description covers the summary and lists JIRA ticket reference, but lacks a before/after comparison section as specified in the template.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sayalibhavsar sayalibhavsar self-assigned this Jun 15, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 `@README.md`:
- Around line 297-314: The warehouse-sizing formulas in the documentation can
produce fractional results from division operations like `end_warehouse / 8` and
the derived `start` calculation `(end_warehouse - (increment * 8)) + increment`,
but warehouse counts must be integral values. Update the documentation to
explicitly specify the rounding behavior applied to these formulas (floor,
ceiling, or standard rounding), clarifying how fractional results are handled.
Apply this clarification consistently to all three sections covering Ending
Warehouse Count, Starting Warehouse Count, and Increment, ensuring readers
understand that the final warehouse values are always integers.
🪄 Autofix (Beta)

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: Enterprise

Run ID: f729d6a0-0b2e-4f22-a5f5-684afddc3e3c

📥 Commits

Reviewing files that changed from the base of the PR and between 3daa368 and 17f6eb5.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
@sayalibhavsar sayalibhavsar changed the title docs: rewrite README following autohpl-wrapper style docs: rewrite README to match wrapper documentation standard Jun 15, 2026
Comprehensive rewrite of the specjbb-wrapper README modeled after the
autohpl-wrapper documentation structure. All content is derived from
the specjbb-wrapper source code.

Adds detailed sections for: command-line options (including all
general_setup options), step-by-step workflow, dependencies with
per-OS Java package matrix, benchmark explanation, output files,
usage examples, warehouse sizing logic, JVM heap sizing, return
codes, and troubleshooting notes. Removes stale pbench references
from the original documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant