lllyasviel / lllyasviel/FramePack
Unable to reproduce advertised 6 GB VRAM requirement
- Dominant language
- Python
- Stars
- 17.3k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Setup:
* GPU: Quadro RTX 4000 (8 GB VRAM)
* CPU: Intel i9‑9880H
* RAM: 128 GB
* OS: Windows 11
* Install method: official Windows installer (update.bat, run.bat), no manual modifications
Reproduction steps:
1. Launch the installer and run with default settings.
2. Provide a 320×200 starting image.
3. Request a 1‑second video (the minimum the UI allows).
4. Other settings at default values (e.g. teacache already checked, etc.)
Observed behavior:
* VRAM usage climbs to ~7.7 GB / 8 GB.
* Shared GPU memory usage climbs to ~62.5 GB / 63.9 GB.
* The process sits at “Starting Sampling…” for 1–2 hours without producing a frame.
* Eventually fails with CUDA: out of memory.
Expected behavior:
* Based on the README, the model should run within 6 GB VRAM, even for much longer clips:
> To generate 1‑minute video (60 seconds) at 30fps (1800 frames) using the 13B model, the minimal required GPU memory is 6 GB. (Yes 6 GB, not a typo. Laptop GPUs are okay.)
Questions:
* Is the Windows installer configured differently from the benchmarked setup?
* Are there additional flags or optimizations (e.g. quantization, low‑VRAM mode) required to achieve the advertised 6 GB usage?
* If so, could the README or installer instructions be updated to clarify the actual requirements and how to enable them?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the README's 6 GB VRAM claim and the Windows installer flow in update.bat and run.bat. Reproduce the 320×200, 1-second generation with default settings, then determine whether the installer differs from the advertised setup or needs documented flags; done means the memory requirement and configuration are clarified.
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
- Mostly clear
- Newbie friendliness
- 42/100