Viewing profile — LuxBennu
LuxBennu
HN member- Joined
- Tue, Sep 24, 2019, 1:35 AM UTC
- HN karma
- 86
- Public activity
- 47 items
- HN profile
- View on Hacker News ↗
About LuxBennu
Recent public activity
- story
-
comment
Comment #48679002
[flagged]
- story
- story
- story
- story
-
comment
Comment #48149200
[flagged]
- story
- story
- story
-
comment
Comment #47786718
Chatgpt for Excel is still an office add-in running in the same sandbox though. strongpigeon described the exact bottleneck upthread, process boundary crossings, context.sync() rou…
-
comment
Comment #47778767
[dead]
- story
-
comment
Comment #47691954
Yeah sorry that was unclear on my part. I chunk at the endpoint level, whisper itself obviously processes 30s windows. The memory/latency thing I was referring to is more about pro…
-
comment
Comment #47682234
Oh nice, the pyannote coreml port is interesting. Last time I looked at pyannote it was pytorch only so getting it to run efficiently on apple silicon was kind of a pain. Does the …
-
comment
Comment #47682225
Ah that makes sense, quadratic scaling is brutal. So with 96gb i'd probably get somewhere around 4-5k total sequence length before hitting the wall, which is still pretty limiting …
-
comment
Comment #47680929
I run whisper large-v3 on an m2 max 96gb and even with just inference the memory gets tight on longer audio, can only imagine what fine-tuning looks like. Does the 64gb vs 96gb mak…
-
comment
Comment #47667650
Yeah that makes sense, chunking on silence would sidestep the latency issue pretty cleanly. I've been running it through a basic fastapi wrapper so it just takes whatever audio blo…
-
comment
Comment #47666857
I've been running whisper large-v3 on an m2 max through a self-hosted endpoint and honestly the accuracy is good enough that i stopped bothering with cleanup models. The bigger ann…
-
comment
Comment #47604717
[dead]
-
comment
Comment #47597922
that tracks with what i've noticed practically. shorter prompts feel basically the same between llama.cpp metal and what i'd expect from native mlx, but once context gets longer th…
-
comment
Comment #47597902
Roughly 8-12 token/s on generation depending on context length. Prompt processing is faster obviously. Haven't benchmarked it super carefully though, just eyeballing the llama.cpp …
-
comment
Comment #47597894
yeah fair point, it's definitely model dependent. i've had good results with qwen but tried it on a smaller mistral variant once and the output quality dropped noticeably even at q…
-
comment
Comment #47592257
good overview of the architecture side but worth mentioning there's another axis that stacks on top of all of this: you can quantize the kv cache itself at inference time. in llama…
-
comment
Comment #47591461
Thanks! Turns out structural signals get you surprisingly far. An LLM catches more, but speed is the feature.