Skip to content

Reduce Vevo2 FM graph peak memory - #443

Merged
0xShug0 merged 1 commit into
mainfrom
fix/vevo2-fm-step-allocator
Sep 4, 2026
Merged

Reduce Vevo2 FM graph peak memory#443
0xShug0 merged 1 commit into
mainfrom
fix/vevo2-fm-step-allocator

Conversation

@0xShug0

@0xShug0 0xShug0 commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Fixes #437

Summary

  • split Vevo2 FM step mutable IO tensors from compute graph temporaries
  • allocate the FM step compute graph with ggml gallocr/liveness allocation instead of allocating every tensor in the graph context
  • release transient FM graph resources after conditioning and final mel read

Validation

Case Result Peak VRAM
pre-fix C++ VC 60s + b.wav failed: requested 82460.49 MiB CUDA allocation n/a
pre-fix C++ SVC 60s + b.wav failed: requested 82460.49 MiB CUDA allocation n/a
after-fix C++ VC 60s + b.wav completed 5289 MiB
after-fix C++ SVC 60s + b.wav completed 5295 MiB
Vevo2 CUDA path tests 4/4 passed, 0 artifact differences vs baseline SVC path 15418 -> 6346 MiB

The 60s validation used a 60-second concat of bundled Vevo2 gallery audio as source and the repo b.wav asset as the reference voice.

@0xShug0
0xShug0 merged commit 7998991 into main Sep 4, 2026
6 checks passed
@0xShug0
0xShug0 deleted the fix/vevo2-fm-step-allocator branch September 4, 2026 05:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

failed to allocate Vevo2 FM step graph

1 participant