Live data from Hacker News

Hypura – A storage-tier-aware LLM inference scheduler for Apple Silicon

github.com

31–40 of 101 posts

Re: Hypura – A storage-tier-aware LLM inference scheduler for Apple Silicon

#31
post #21

Earlier quoted context omitted.

Don't post generated/AI-edited comments. HN is for conversation between humans https://news.ycombinator.com/item?id=47340079

That doesn't read like an AI-generated comment to me. He did mention he vibe-coded the project but that's not against the guidelines.

It's either written by an LLM, or written by someone who learned to write by reading LLM output

Re: Hypura – A storage-tier-aware LLM inference scheduler for Apple Silicon

#32
post #21

Earlier quoted context omitted.

Don't post generated/AI-edited comments. HN is for conversation between humans https://news.ycombinator.com/item?id=47340079

That doesn't read like an AI-generated comment to me. He did mention he vibe-coded the project but that's not against the guidelines.

Vibe-coded project is fine.

At least prompt your LLM to dodge the obvious tells when commenting!

Re: Hypura – A storage-tier-aware LLM inference scheduler for Apple Silicon

#33
You do not provide any comparison to llama.cpp with mmap.

You do not explain how any kind of predictor can work for MoE experts.

You do not explain how prediction can even be useful. I can predict the layers used in a dense model (all of them are used in order), but that doesn't help me much. It's still bottlenecked on bandwidth (hint: MoE doesn't change this).

Re: Hypura – A storage-tier-aware LLM inference scheduler for Apple Silicon

#35

OS paging would be significantly worse here. The kernel's page fault handler is reactive — it doesn't know you're about to read layer 47's FFN weights, so it can't prefetch. You stall on every fault, wait for the 4KB/16KB page to load, then resume. With 80 layers of dense FFN streaming, that's thousands of cold faults per token. What makes this approach faster is that the model's access pattern is completely determin…

That assumes you have significant work to do between fetches (so you can prefetch while using the current data). With LLM decode you don't.

Re: Hypura – A storage-tier-aware LLM inference scheduler for Apple Silicon

#36

OS paging would be significantly worse here. The kernel's page fault handler is reactive — it doesn't know you're about to read layer 47's FFN weights, so it can't prefetch. You stall on every fault, wait for the 4KB/16KB page to load, then resume. With 80 layers of dense FFN streaming, that's thousands of cold faults per token. What makes this approach faster is that the model's access pattern is completely determin…

[deleted]

Re: Hypura – A storage-tier-aware LLM inference scheduler for Apple Silicon

#37

It will be interesting to compare this to https://news.ycombinator.com/item?id=47476422 and https://news.ycombinator.com/item?id=47490070 . Very similar design except that this is apparently using mmap, which according to the earlier experiment incurs significant overhead.

Except this isnt using heavily quantised versions of the model thus reducing quality.
Post reply on HN