Viewing profile — Argonautlabs
Argonautlabs
HN member- Joined
- Tue, Sep 08, 2026, 8:02 PM UTC
- HN karma
- 177
- Public activity
- 18 items
- HN profile
- View on Hacker News ↗
About Argonautlabs
No profile information was provided.
Recent public activity
-
comment
Comment #49632380
Often Deep Seek V4 flash or Qwen should be enough. I wanted to see whether Kimi runs at all on one machine with the full record published, and for long multi-table finance reasonin…
-
comment
Comment #49632221
[flagged]
-
comment
Comment #49632147
[dead]
-
comment
Comment #49618395
OWC Express 1M2 (Thunderbolt 5, single M.2 NVMe) — three of them, two on the Mac's own ports and one behind an OWC Thunderbolt 5 hub since the machine has three ports. Each enclosu…
-
comment
Comment #49618314
In principle yes, and the upstream engine already has a CUDA path with expert streaming and residency (that's theirs, not ours — we only measured on this Mac). Two things carry ove…
-
comment
Comment #49617993
Just internal 2Tb Macbook M5 Max drive it came in at roughly half the four-drive speed (0.535 vs 1.038 tok/s at 128 tokens), since one fast drive still has to serve all 16 reads pe…
-
comment
Comment #49617870
Memory, not the model. The KV cache on this engine grows about 2.8 MiB per token of context, and the machine's 128 GB is already holding the 50.7 GiB resident trunk plus reserves t…
-
comment
Comment #49617821
Thank you. Put a five-line TL;DR at the top of the README — what it is, the number, the honest limit, the two findings, credits — with the detail below for anyone who wants it.
-
comment
Comment #49617542
Fair, and we didn't measure it. Decode was flat from 128 to 512 generated tokens (0.926 → 0.923 tok/s drafter-off), but that's a 6-token prompt plus the output — total context unde…
-
comment
Comment #49617497
That's the one workload this setup is worst at today, unfortunately: output tokens are cheap at 1/s but input isn't — a 512-token prompt takes ~6 minutes before the first token, be…
-
comment
Comment #49617459
Probably not. Each read here is a whole 17.5 MB expert file, so the time per read is set by the drive's throughput, not its access latency — 17.5 MB at 7 GB/s is ~2.5 ms, which is …
-
comment
Comment #49617397
Bandwidth doesn't multiply like that here, and we measured it rather than assumed it. A MoE layer needs 16 expert reads and can't proceed until the slowest one lands, so a layer co…
-
comment
Comment #49617091
SSDs are connected via Thunderbolt 5 enclosures. I have one Gen4 and three Gen5 ssds inside enclosures. You can see specs here https://github.com/argonautlabsai/deltafin/tree/main/…
-
comment
Comment #49617014
Thank you! Here is the short version: Kimi K3, 2.78T parameters, ~1.45 TB of MXFP4 experts streamed from four SSDs on an M5 Max / 128 GB. 1.00 tok/s steady over 512 tokens, 1.13 ov…
-
comment
Comment #49616773
It actully does the job. Example: every morning it takes 30-40 minutes to generate reports automatically and these reports are being sent as a pdf to read to Telegram.
-
comment
Comment #49616520
Not useful for chat, agreed — and I wouldn't pretend otherwise. It's useful for the other kind of work: scheduled, unattended jobs where nobody is waiting on the cursor. My use is …
-
comment
Comment #49616265
Author here. Some context and the caveats up front. The model is Kimi K3, 2.78T parameters, ~1.45 TB of expert weights. It does not fit in memory, so the experts stream from disk: …
- story