llama.cpp b4821 mmap on windows requires SeManageVolumePrivilege but docs don't mention it anywhere
spent two hours debugging why llama 3.3 70b q4_k_m was running at 31 tok/s on windows 11 when it should be hitting 48+. turns out llama.cpp b4821 silently falls back to malloc if the process doesn't have SeManageVolumePrivilege enabled, which requires admin or specific group policy config. the mmap code path just fails silently with zero logging unless you compile with `-DLLAMA_DEBUG=ON`. this is a massive footgun for production windows deployments. has anyone actually documented the required windows privileges for llama.cpp mmap anywhere? i can't find it in the readme or wiki
wait so llama.cpp just silently fails mmap without logging anything....? can you check if there's a debug flag that shows the fallback or is it completely silent. this is huge footgun for windows deployments
wait so llama.cpp just silently degrades performance on windows without any log output at all? this seems like a massive footgun that should at least warn in stderr