@FIR-736 - lama.cpp: Disable all logs except token generation log #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Logs are being initialized at different levels across llama.cpp, GGML, and other components, and in some places, they are being re-initialized. For now, this is what I’ve identified to suppress the logs, but we’ll continue to improve it as we understand the system better.
Currently we are getting below Logs
########
[akapoor@wssw01 llama.cpp]$ ./build-posix/bin/llama-cli -p "my cat’s name" -m /proj/rel/sw/ggml/models/tinyllama-vo-5m-para.gguf --device none -c 12288 --temp 0.0 --n-predict 4 --repeat-penalty 1.5 -b 1024 --top-k 50 --top-p 0.9 --repeat-last-n 5 --no-warmup
my cat’s name was Tim. He
llama_perf_sampler_print: sampling time = 7.42 ms / 10 runs ( 0.74 ms per token, 1348.44 tokens per second)
llama_perf_context_print: load time = 140.56 ms
llama_perf_context_print: prompt eval time = 5.62 ms / 6 tokens ( 0.94 ms per token, 1068.57 tokens per second)
llama_perf_context_print: eval time = 6.89 ms / 3 runs ( 2.30 ms per token, 435.54 tokens per second)
llama_perf_context_print: total time = 156.70 ms / 9 tokens
[akapoor@wssw01 llama.cpp]$