Skip to content

dashboard: use "stress test" instead of "pressure test" (#23399) - #23478

Merged
ti-chi-bot[bot] merged 1 commit into
pingcap:masterfrom
ti-chi-bot:cherry-pick-23399-to-master
Aug 10, 2026
Merged

dashboard: use "stress test" instead of "pressure test" (#23399)#23478
ti-chi-bot[bot] merged 1 commit into
pingcap:masterfrom
ti-chi-bot:cherry-pick-23399-to-master

Conversation

@ti-chi-bot

Copy link
Copy Markdown
Member

This is an automated cherry-pick of #23399

What is changed, added or deleted? (Required)

"Pressure test" is not idiomatic English for software performance testing — in software contexts the standard term is stress test (or load test); "pressure test" primarily belongs to mechanical/physical engineering (pressure vessels, pipes). Here it reads as a literal rendering of the Chinese 压力测试, which means "stress test".

This PR renames the 5 go-ycsb pressure test occurrences to stress test, matching the "stress test" wording already used elsewhere in the docs:

  • dashboard/dashboard-diagnostics-usage.md (4)
  • information-schema/information-schema-metrics-summary.md (1)

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v8.5 (TiDB 8.5 versions)
  • v8.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 versions)
  • v8.2 (TiDB 8.2 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

  • Other reference link(s): companion to the Japanese i18n-ja-release-8.5 cleanup (the ja side was renamed 圧力テスト → 負荷テスト).

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

Summary by CodeRabbit

  • Documentation
    • Updated diagnostic usage examples to consistently refer to go-ycsb “stress tests” instead of “pressure tests.”
    • Revised the information schema metrics summary to use the same terminology.

"Pressure test" is not idiomatic English for software performance testing
(it reads as a literal rendering of the Chinese 压力测试). The go-ycsb
performance runs described here are stress tests; the docs already use
"stress test" elsewhere. Rename the 5 "pressure test" occurrences to
"stress test" in dashboard-diagnostics-usage.md and
information-schema-metrics-summary.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@ti-chi-bot ti-chi-bot added lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. ONCALL Relates to documentation oncall. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-master This PR is cherry-picked to master from a source PR. type/enhancement The issue or PR belongs to an enhancement. labels Aug 10, 2026
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@lilin90 lilin90 assigned lilin90 and unassigned yahonda Aug 10, 2026

@lilin90 lilin90 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/approve

@ti-chi-bot

ti-chi-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lilin90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added the approved label Aug 10, 2026
@ti-chi-bot
ti-chi-bot Bot merged commit 0b90679 into pingcap:master Aug 10, 2026
12 checks passed
@ti-chi-bot
ti-chi-bot Bot deleted the cherry-pick-23399-to-master branch August 10, 2026 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. ONCALL Relates to documentation oncall. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-master This PR is cherry-picked to master from a source PR. type/enhancement The issue or PR belongs to an enhancement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants