docs: Add README for distributed-micro-benchmark

[PranjalC100]

Added distributed-micro-benchmark/README.md to explain how to use run.sh, how to test different GCSFuse commits, test cases, and mount configs, while explicitly noting that Kokoro scripts are meant for CI/CD and should not be manually modified. Also updated the root README.md to link to the new documentation.

---

PR created automatically by Jules for task 13681364194033677783 started by @PranjalC100

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 significantly enhances the documentation for the distributed micro-benchmark, making it more accessible and user-friendly. It provides clear guidance on how to execute, customize, and interpret performance tests for GCSFuse, ensuring that users can effectively leverage the benchmarking tools to understand and evaluate GCSFuse performance under various configurations.

Highlights

• New Documentation for Distributed Micro-Benchmark: A new README.md file was added to the distributed-micro-benchmark directory, providing comprehensive documentation for running and customizing GCSFuse performance tests.
• Root README Update: The main README.md at the repository root was updated to include a link and a brief description of the distributed-micro-benchmark directory, pointing to its new documentation.
• Benchmark Usage and Customization: The new documentation details how to use run.sh with various options (e.g., specifying GCSFuse commits, running read/write benchmarks) and how to customize tests by modifying FIO parameters, GCSFuse mount configurations, and FIO job files.
• CI/CD Script Clarification: The distributed-micro-benchmark/README.md explicitly notes that kokoro_* scripts are intended for automated CI/CD processes and should not be manually modified for benchmark runs.

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.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the main README.md to include a description of the repository and adds a new, comprehensive README.md for the distributed-micro-benchmark directory, detailing its overview, usage, customization, infrastructure configuration, and result analysis. The review suggests ensuring consistent casing for 'gcsfuse' and adding a newline character at the end of both README.md files.