afaik ollama relies on llama.cpp and mmap. mmap loads pages on demand and doesn't use the same explicit cache or parallel reads like my engine. Most likely ollama/llama.cpp will be way slower in this case
not with this engine. Kimi is a very different model. You can try to check HN later, I believe someone will build engine for this model for edge devices
m5 device also uses the same approach. the same 16 cache slots. and experts are evicted from memory as needed. And activity monitor shows 2gb usage for m5 pro (24gb btw)
Yeah, correct! You can set up this engine to get more expert cache slots (e.g 32 instead of 16) to get a better hit rate and better tok/s.
it will be 3.5gb instead of 2gb.
I think it will throttle quite soon, but I haven't tried runs longer than 30minutes with this engine.
However, there is no constant load on ssd or gpu. i/o and gpu work are alternating and there is a brief idle periods for each i/o and gpu during inference (because gpu waits for i/o and after that i/o waits for gpu)
For Mac I would start from MLX engine.
For exact model choice it is better to check bench results, and select model based on your need. A lot of good feedback about Qwen3.6, but I haven't used it in my tasks
I saw a pretty cool project to run an llm on an esp32 device https://github.com/slvDev/esp32-ai