Skip to content

faq: correct fio examples for psync#22485

Merged
ti-chi-bot[bot] merged 1 commit into
pingcap:masterfrom
hfxsd:fio-iodepth-and-ioengine
Feb 25, 2026
Merged

faq: correct fio examples for psync#22485
ti-chi-bot[bot] merged 1 commit into
pingcap:masterfrom
hfxsd:fio-iodepth-and-ioengine

Conversation

@hfxsd

@hfxsd hfxsd commented Feb 25, 2026

Copy link
Copy Markdown
Collaborator

First-time contributors' checklist

What is changed, added or deleted? (Required)

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

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 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)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

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

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

@hfxsd hfxsd self-assigned this Feb 25, 2026
@ti-chi-bot ti-chi-bot Bot added contribution This PR is from a community contributor. missing-translation-status This PR does not have translation status info. labels Feb 25, 2026
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @hfxsd, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the fio command examples within the documentation for testing TiKV instance disk performance. The changes specifically target the psync I/O engine, providing more accurate and recommended configurations to ensure reliable and consistent performance measurements.

Highlights

  • Corrected fio examples: Updated fio command examples for disk performance testing of TiKV instances, specifically for the psync I/O engine, to ensure accurate and recommended configurations.
  • Added psync explanation: Included an introductory note explaining the recommended parameters like iodepth=1, direct=1, and time_based when using ioengine=psync in fio tests.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • faq/deploy-and-maintain-faq.md
    • Added a descriptive paragraph explaining the use of ioengine=psync with iodepth=1 and direct=1.
    • Modified the "Random Read test" fio command to include direct=1 and time_based, and set iodepth=1.
    • Modified the "The mix test of sequential Write and random Read" fio command to include direct=1 and time_based, and set iodepth=1.
Activity
  • PR created by hfxsd.
  • Translated from pingcap/docs-cn/pull/21383.
  • Targets master and v8.5 branches for documentation updates.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@ti-chi-bot ti-chi-bot Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 25, 2026
@hfxsd hfxsd added translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. and removed missing-translation-status This PR does not have translation status info. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 25, 2026
@ti-chi-bot

ti-chi-bot Bot commented Feb 25, 2026

Copy link
Copy Markdown

@hbisheng: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

The pull request effectively corrects the fio examples for psync I/O, enhancing their technical accuracy and relevance for testing disk performance. The addition of a descriptive paragraph provides valuable context for the changes, explaining the rationale behind using iodepth=1 and direct=1 with psync. The modifications to the fio commands, including the removal of -fdatasync=1 and the addition of -direct=1 and -time_based, align with best practices for synchronous I/O benchmarking. Overall, these changes significantly improve the clarity and correctness of the documentation.

@hfxsd hfxsd requested a review from qiancai February 25, 2026 06:38
@ti-chi-bot

ti-chi-bot Bot commented Feb 25, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-02-25 06:40:52.680850437 +0000 UTC m=+250725.195645066: ☑️ agreed by qiancai.

@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Feb 25, 2026
@ti-chi-bot

ti-chi-bot Bot commented Feb 25, 2026

Copy link
Copy Markdown

@LykxSassinator: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@hfxsd hfxsd added the lgtm label Feb 25, 2026
@hfxsd

hfxsd commented Feb 25, 2026

Copy link
Copy Markdown
Collaborator Author

/approve

@ti-chi-bot

ti-chi-bot Bot commented Feb 25, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hfxsd

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 Feb 25, 2026
@ti-chi-bot ti-chi-bot Bot merged commit f08e1e2 into pingcap:master Feb 25, 2026
11 of 12 checks passed
@ti-chi-bot

Copy link
Copy Markdown
Member

In response to a cherrypick label: new pull request created to branch release-8.5: #22487.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved contribution This PR is from a community contributor. lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants