lllyasviel / lllyasviel/stable-diffusion-webui-forge

AMD GPU does not use 100% of its power when using SDXL models

Open
#404 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

AMD
Dominant language
Python
Stars
13k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

### Checklist

- [ ] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [ ] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

my AMD GPU doesn't use the 100% when use SDXL models while generating images

### Steps to reproduce the problem

1. select sdxl model
2. type prompt
3. click on generat

### What should have happened?

should generate image using 100% of the gpu power

### What browsers do you use to access the UI ?

_No response_

### Sysinfo

[sysinfo-2024-02-25-19-35.json](https://github.com/lllyasviel/stable-diffusion-webui-forge/files/14397564/sysinfo-2024-02-25-19-35.json)

### Console logs

```Shell
Calculating sha256 for C:\a1111\webui_forge_cu121_torch21\webui\models\Stable-diffusion\juggernautXL_version6Rundiffusion.safetensors: 1fe6c7ec54c786040cdabc7b4e89720069d97096922e20d01f13e7764412b47f
Loading weights [1fe6c7ec54] from C:\a1111\webui_forge_cu121_torch21\webui\models\Stable-diffusion\juggernautXL_version6Rundiffusion.safetensors
model_type EPS
UNet ADM Dimension 2816
Using split attention in VAE
Working with z of shape (1, 4, 32, 32) = 4096 dimensions.
Using split attention in VAE
extra {'cond_stage_model.clip_l.logit_scale', 'cond_stage_model.clip_l.text_projection', 'cond_stage_model.clip_g.transformer.text_model.embeddings.position_ids'}
To load target model SDXLClipModel
Begin to load 1 model
Moving model(s) has taken 0.02 seconds
Model loaded in 99.0s (unload existing model: 1.1s, calculate hash: 7.1s, load weights from disk: 1.0s, forge load real models: 87.7s, forge finalize: 0.1s, load textual inversion embeddings: 0.2s, calculate empty prompt: 1.7s).
To load target model SDXL
Begin to load 1 model
[Memory Management] Current Free GPU Memory (MB) = 1024.0
[Memory Management] Model Memory (MB) = 9794.134841918945
[Memory Management] Minimal Inference Memory (MB) = 1024.0
[Memory Management] Estimated Remaining GPU Memory (MB) = -9794.134841918945
[Memory Management] Requested SYNC Preserved Memory (MB) = 0.0
[Memory Management] Parameters Loaded to SYNC Stream (MB) = 9794.096694946289
[Memory Management] Parameters Loaded to GPU (MB) = 0.0
Moving model(s) has taken 0.08 seconds
68%|███████████████████████████████████████████████████████▊ | 17/25 [13:36<06:44, 50.57s/it]
Total progress: 68%|████████████████████████████████████████████▉ | 17/25 [12:30<06:43, 50.48s/it]
```

### Additional information

_No response_

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 source files or tests are named. Start by reproducing SDXL generation on the reported AMD setup with extensions disabled, then use the linked sysinfo and console log to investigate GPU memory and utilization; done means the cause is identified and generation uses the expected GPU resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
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.