Update PaddleOCR-VL.md for AMD GPU

[haic0]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @haic0, 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 enhances the PaddleOCR-VL.md documentation by integrating a dedicated guide for AMD GPU users. The new content outlines the necessary steps to configure a Docker environment, authenticate with Hugging Face, launch the vLLM server with specific optimizations, and conduct performance benchmarks, thereby expanding the hardware compatibility and usability of PaddleOCR-VL.

Highlights

• AMD GPU Support: Added a new, comprehensive section to the PaddleOCR-VL.md documentation detailing how to set up and run PaddleOCR-VL models on AMD MI300X GPUs.
• Docker Environment Setup: Provided instructions for preparing the Docker environment, including pulling the rocm/vllm-dev:nightly image and launching the container with necessary privileges and device mappings.
• vLLM Server Configuration: Included specific commands and environment variables for starting the vLLM server, such as SAFETENSORS_FAST_GPU=1 and VLLM_USE_V1=1, along with parameters like --max-num-batched-tokens and --no-enable-prefix-caching.
• Benchmarking Guide: Detailed steps for running a benchmark script within the Docker container to evaluate performance of PaddleOCR-VL on AMD GPUs.

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

[gemini-code-assist]

Code Review

This pull request adds a new section to the PaddleOCR-VL.md documentation with instructions on how to run the model on AMD GPUs. The guide is well-structured and provides clear, step-by-step commands. My review includes a few suggestions to improve the formatting and correct a duplicated command-line argument.

[gemini-code-assist]

These two blank lines are unnecessary. Removing them will improve formatting consistency, leaving two blank lines before the next section, which is sufficient.

[gemini-code-assist]

This extra blank line can be removed to improve formatting consistency. One blank line is sufficient to separate the code block from the heading.

[Isotr0py]

Can you address gemini's format comments?

[haic0]

@Isotr0py Thanks! I've updated it based on your suggestions. Could you check, Tks!