modelscope / modelscope/DiffSynth-Studio

Low GPU-Util and Save Promblem During Full training on Qwen-Image-Edit-2509

Open
#1,049 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
13.1k
Forks
1.3k
Avg merge
13h 12m
Merged PRs (30d)
45

Description

Hi,

Thanks for your excellect framework!

I’m fine-tuning Qwen-Image-Edit-2509 on a self-built image editing dataset, but the training speed is extremely slow.

Environment: single node with 8 GPUs

Dataset size: ~1M samples

Estimated training time: ~1300 hours (very slow)

As shown in the attached nvitop screenshot, GPU utilization is very low across all devices.

Image

Is this expected for this model, or could there be an inefficiency in data loading / communication?
Any suggestions or optimization tips to improve multi-GPU utilization would be greatly appreciated.

Additionally, When performing full fine-tuning, saving model weights is extremely slow — only one GPU shows high utilization during the saving stage, and the process often triggers NCCL timeout errors, blocking the training.

Is there a recommended way to handle or accelerate checkpoint saving in multi-GPU fine-tuning?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by reproducing full fine-tuning on the reported single-node, eight-GPU setup and inspect data loading, communication, and checkpoint-saving stages. Done means identifying the cause of low utilization and NCCL timeouts and documenting a validated optimization or workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
distributed-systems, machine-learning, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.