In mac it falls back to CPU. Any ideas?

#16
by Grossor - opened

I get this. And... well its CPU speed. Only 7 tokens per second. Any ideas on how to fix this?

Select a model to view its output...
0.00.051.324 I cmn common_param: common_params_print_info: verbosity = 3 (adjust with the -lv N CLI arg)
0.00.051.611 W srv llama_server: -----------------
0.00.051.612 W srv llama_server: CORS is set to allow all origins ('*') and no API key is set
0.00.051.612 W srv llama_server: this can be a security risk (cross-origin attacks)
0.00.051.612 W srv llama_server: more info: https://github.com/ggml-org/llama.cpp/pull/25655
0.00.051.613 W srv llama_server: -----------------
0.00.060.882 I srv load_model: loading model '/Volumes/4TBSamsungSSD990/gguf/DeepSeekV4Flash-0731-Q8KXL/UD-Q8_K_XL/DeepSeek-V4-Flash-0731-UD-Q8_K_XL-00001-of-00005.gguf'
1.04.477.282 W resolve_fused_ops: layer 2 is assigned to device MTL0 but Lightning Indexer is assigned to device CPU (usually due to missing support)
1.04.477.290 W resolve_fused_ops: Lightning Indexer not supported, set to disabled
1.04.479.354 W resolve_fused_ops: layer 0 is assigned to device MTL0 but fused DeepSeek V4 HC pre is assigned to device CPU (usually due to missing support)
1.04.479.355 W resolve_fused_ops: fused DeepSeek V4 HC pre not supported, set to disabled
1.04.481.839 W resolve_fused_ops: layer 0 is assigned to device MTL0 but fused DeepSeek V4 HC comb is assigned to device CPU (usually due to missing support)
1.04.481.840 W resolve_fused_ops: fused DeepSeek V4 HC comb not supported, set to disabled
1.04.513.106 W resolve_fused_ops: layer 0 is assigned to device MTL0 but fused DeepSeek V4 HC post is assigned to device CPU (usually due to missing support)
1.04.513.108 W resolve_fused_ops: fused DeepSeek V4 HC post not supported, set to disabled
1.06.058.936 I srv load_model: initializing, n_slots = 4, n_ctx_slot = 100096, kv_unified = 'true'
1.06.064.115 I srv llama_server: model loaded
1.06.064.117 I srv llama_server: listening on http://0.0.0.0:8504

Sign up or log in to comment