DZRobo
commited on
Commit
·
bcae778
1
Parent(s):
8ca0a45
Update hardware requirements section in README
Browse filesRevised the hardware requirements section to provide more practical guidance, including tested hardware configurations and recommendations for managing starting latency to avoid errors during upscaling.
README.md
CHANGED
|
@@ -60,11 +60,11 @@ Photo Dog
|
|
| 60 |
<b>I highly recommend working with SmartSeed.</b>
|
| 61 |
- CADE2.5 pipeline does not just upscale the image, it iterates and adds small details, doing it carefully, at every stage.
|
| 62 |
|
| 63 |
-
## Hardware
|
| 64 |
-
-
|
| 65 |
-
-
|
| 66 |
- Notes
|
| 67 |
-
- Lowering the starting latent (e.g., 512x768) reduces both VRAM and RAM.
|
| 68 |
- Disabling hi-res depth/edges (ControlFusion) reduces peaks. (not recommended!)
|
| 69 |
- Depth weights add a bit of RAM on load; models live under `depth-anything/`.
|
| 70 |
|
|
|
|
| 60 |
<b>I highly recommend working with SmartSeed.</b>
|
| 61 |
- CADE2.5 pipeline does not just upscale the image, it iterates and adds small details, doing it carefully, at every stage.
|
| 62 |
|
| 63 |
+
## Hardware
|
| 64 |
+
- The pipeline is designed for good hardware (tested on RTX5090 (32Gb) and RAM 92Gb), try to keep the starting latency very small, because there is an upscale at the steps and you risk getting errors if you push up the starting values.
|
| 65 |
+
- start latent ~ 672x944 -> final ~ 3688x5192 across 4 steps.
|
| 66 |
- Notes
|
| 67 |
+
- Lowering the starting latent (e.g., 512x768) or lower, reduces both VRAM and RAM.
|
| 68 |
- Disabling hi-res depth/edges (ControlFusion) reduces peaks. (not recommended!)
|
| 69 |
- Depth weights add a bit of RAM on load; models live under `depth-anything/`.
|
| 70 |
|