[Log] add log about gpu worker init snapshot and requested memory

[andyxning]

Purpose

Add detailed log about each gpu worker init snapshot and requested memory in favor of easily debug.

Test Plan

NA

Test Result

NA

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.

[gemini-code-assist]

Code Review

This pull request adds two log lines to gpu_worker.py to provide details about memory initialization. My review focuses on improving the readability and conciseness of these logs to make them more effective for debugging, which is the stated purpose of the PR. I've suggested formatting the memory values in GiB, consistent with other logging in the file, instead of using the default repr.

[gemini-code-assist]

The new log messages for the memory snapshot and requested memory are very verbose due to the use of !r on a dataclass without a custom __repr__. This makes them hard to read and inconsistent with other memory-related logs in the file, which typically format memory sizes in GiB for better readability. To improve clarity and align with existing logging practices, it's better to format the output into a single, more concise log message, converting byte values to GiB.

            GiB = lambda b: round(b / GiB_bytes, 2)
            logger.info(
                "Initial memory: free=%sGiB, total=%sGiB, requested=%sGiB.",
                GiB(self.init_snapshot.free_memory),
                GiB(self.init_snapshot.total_memory),
                GiB(self.requested_memory),
            )

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @andyxning.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[chaunceyjiang]

/cc @DarkLight1337 PTAL.

[mergify]

Hi @andyxning, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy or markdownlint failing?

mypy and markdownlint are run differently in CI. If the failure is related to either of these checks, please use the following commands to run them locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10
# For markdownlint
pre-commit run --hook-stage manual markdownlint

[mergify]

Hi @andyxning, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy or markdownlint failing?

mypy and markdownlint are run differently in CI. If the failure is related to either of these checks, please use the following commands to run them locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10
# For markdownlint
pre-commit run --hook-stage manual markdownlint

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @andyxning.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[andyxning]

Finally, ci is green. @DarkLight1337 PTAL.