why it's painfully slow on RTX with 12gb Vram?

#5
by WhatABigWorld - opened

I found the windows installer which saved my day "Comni-v1.0.22-win64.exe"
I downloaded
the MiniCPM-o-4_5-Q4_K_M.gguf and the other folder except for the weights folder which I think it's apple related
the Comni reads all tts llm vision and detcted my gpu rtx 12gb fine but when I start the server button it takes 4 to 5 minutes to load
if it's only for the first time that's gonna be fine for me but after I use the user interface and I use any of the 4 categories it's paniful it take ages to respond or to move from state to another like from start to live.
and if it respond it might do it once then it give silence for ever
I also noticed that this whole setup utlize only 13% of my gpu usage or none , same on cpu
in contrary I run llms on the same gpu much much faster so what's going ?

WhatABigWorld changed discussion title from why it's paninfully slow on 12g Vram? to why it's painfully slow on 12gb Vram?
WhatABigWorld changed discussion title from why it's painfully slow on 12gb Vram? to why it's painfully slow on RTX with 12gb Vram?
OpenBMB org

Thanks for the report. Skipping weights/ is fine — that path is Apple/CoreML only. Comni seeing LLM / Vision / TTS on your RTX is expected.

This is a heavier workload than a normal LLM on the same GPU. Full Omni loads LLM + vision + audio + TTS + token2wav together. Q4_K_M is around ~9GB VRAM; on Windows a 12GB card also loses some memory to the desktop, so layers often get offloaded to CPU. That matches the slow first load, slow start → live, GPU at 13% or 0%, and a regular LLM feeling much faster.

“Answers once, then silence” is usually the live/duplex audio path getting stuck, not just low tok/s.

A new Comni app is in the works and should handle this Windows / 12GB setup more cleanly. Please try that build when it lands.

thanks for being so active and for working on solving hat

Sign up or log in to comment