You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
It appears context memory usage can be trivially halved by using fp16? #146
I'm not fully familiar with this codebase, so pardon if I'm wrong. My first attempt to modify the code was to expand hardcoded context window of 512 to 4096 but additional memory usage was not pleasant.
New memory usage is reportedly ggml ctx size = 6065.34 MB and task manager agrees. That's 2GB down.
So far everything is working, no crashes and no degradation in quality. Is there any reason to not do that?
Reacted by Felipe S. S. Schneider
Reacted by Ronsor, Mrroot3r, Jed Fox, Soul_of_Rubber, Micheál Keane, Jonathan Mackenzie, MLTQ, Erik Scholz, hx507, Urammar and 1 more
Activity
Merge pull request ggml-org#146 from admu-progvar/master
IQ2_K_R4 (ggml-org#146)
openvino: OV 2026.2, context-shift, Q5_1 support, gemma4 dense/embedd…
openvino: OV 2026.2, context-shift, Q5_1 support, gemma4 dense/embedd…
openvino: OV 2026.2, context-shift, Q5_1 support, gemma4 dense/embedd…
openvino: OV 2026.2, context-shift, Q5_1 support, gemma4 dense/embedd…
ggml-hrx: size fused router launch for target expert tiles (#146)