Testing executed on the Exynos 5422-powered ODROID-HC1 using llama.cpp build 925e11799.
| Execution Mode | Thread Config | Prompt Processing (pp512) | Text Generation (tg128) |
|---|---|---|---|
| Unbound CPU | -t 4 |
4.48 t/s | 2.42 t/s |
| Pinned to Cortex-A15 OPTIMAL | taskset -c 4-7 -t 4 |
4.49 t/s | 2.55 t/s (+5.4%) |
The Exynos 5422 features a big.LITTLE architecture (4× Cortex-A7 + 4× Cortex-A15). Threading matrix multiplication across all 8 cores forces the 4 high-performance A15 cores to wait on the slower A7 cores at layer synchronization boundaries. Pinning execution strictly to cores 4–7 combined with the HC1's massive aluminum frame thermal dissipation yields maximum tokens-per-second.
taskset -c 4-7 ./build/bin/llama-completion -m qwen0.5b.gguf -p "The top 3 reasons to use a single-board computer are:" -t 4
taskset -c 4-7 ./build/bin/llama-completion -m qwen0.5b.gguf \
-p "Summarize what this website is about in 2 sentences based ONLY on this text:\n\n$(curl -sL https://webcentive.com | sed 's/<[^>]*>/ /g' | tr -s ' ' | head -n 30)" \
-t 4 -no-cnv -n 128
If your documents exceed what fits in memory (or are in PDF/Word format), you cannot feed them raw into llama-completion. Instead, use Retrieval-Augmented Generation (RAG) to query document collections directly from your HC1's local storage:
Install lightweight libraries to chunk PDF/Word files and retrieve relevant snippets:
pip install llama-cpp-python langchain pypdf
qwen0.5b.gguf to keep memory consumption minimal.llama-retrieval Toolllama.cpp includes a built-in vector utility for search:
llama-retrieval binary converts raw text files into vector embeddings.