dashboard: use "stress test" instead of "pressure test"

[yahonda]

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jackysp for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 97bcbf8b-38df-4f4c-8f89-ab22f5452cf7

📥 Commits

Reviewing files that changed from the base of the PR and between 2e1cff6 and f8fdc75.

📒 Files selected for processing (2)

• dashboard/dashboard-diagnostics-usage.md
• information-schema/information-schema-metrics-summary.md

---

📝 Walkthrough

Walkthrough

The documentation now uses “stress test” instead of “pressure test” in dashboard diagnostic examples and an information schema workload description.

Changes

Stress test terminology updates

Layer / File(s)	Summary
Update diagnostic workload terminology dashboard/dashboard-diagnostics-usage.md, information-schema/information-schema-metrics-summary.md	Updated five workload descriptions from “pressure test” to “stress test”.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main terminology change from "pressure test" to "stress test."
Description check	✅ Passed	The description covers the required change, affected version, references, AI involvement, and repository checklist sections.
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.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}