Live data from Hacker News

Viewing profile — throwdbaaway

throwdbaaway

HN member
Joined
Mon, Feb 24, 2020, 1:37 PM UTC
HN karma
444
Public activity
292 items

About throwdbaaway

No profile information was provided.

Recent public activity

  1. comment
    Comment #49121960

    Objectively speaking, the 2 bit quant from antirez has very low accuracy. Meanwhile, his 4 bit quant does have decent accuracy, but is a bit pointless by being bigger than the full…

  2. comment
    Comment #49071074

    They need to get a license from moonshot to provide inference for K3. Probably have to follow the pricing set by moonshot as well.

  3. comment
    Comment #49003694

    It works, thanks to https://github.com/ikawrakow/ik_llama.cpp/pull/1911 , which got merged in early June. However, there might still be some issue with the chat template.

  4. comment
    Comment #48972535

    I suspect this is why DeepSeek had to introduce the 2x peak hours pricing. The price would be too low otherwise.

  5. comment
    Comment #48912288

    Yeah antirez made a lot of big claims in that paragraph. Sounds like a case of AI psychosis.

  6. comment
    Comment #48862081

    If you max out the ram, TG with q3 should be at least 10 t/s. And with dsa, it can still stay close to that number as the context grows.

  7. comment
    Comment #48820367

    That's exactly what I said. They do care when FLOPs are involved. Restoring an old session with 900k tokens will require a lot of FLOPs to reprocess the 900k token. Meanwhile, they…

  8. comment
    Comment #48814659

    Different sessions. With https://github.com/fairydreaming/llama.cpp/tree/dsv4 , 1M context with DSV4 Flash takes less than 6GB of VRAM. I can't run DSV4 Pro, but it should take les…

  9. comment
    Comment #48814069

    Well I wouldn't call it a low bar, since some of the edits were quite complex. And 1M context in less than 6GB of VRAM is truly impressive, but somehow this gets way less attention…

  10. comment
    Comment #48811988

    While we are all speculating, Boris kindly provided some guidance in https://news.ycombinator.com/item?id=47880089 > The challenge is: when you let a session idle for >1 hour, when…

  11. comment
    Comment #48811846

    Indeed they are all lossy. Not sure how much they contribute to the quality loss in long context though. I got a 700k session with DSV4 Pro (official API), and the model was still …

  12. comment
    Comment #48811635

    The current top comment in https://lobste.rs/s/ua1gxl/glm_5_2_coming_ai_margin_collapse correctly zoomed into cached input tokens, but landed on the opposite conclusion: > That is,…

  13. comment
    Comment #48811532

    Seems like a pretty pointless post that still centers around output tokens. In agentic coding, cached input tokens is 90% of the API "cost". It doesn't require GPU compute, and Dee…

  14. comment
    Comment #48781759

    And somehow they claimed that it is "lossless".

  15. comment
    Comment #48640037

    On ZFS with zstd compression, I am getting 1.34x compressratio for the BF16 weights (across multiple models). Here's the du output for GLM-5.2: $ du -s -BG /cube/models/zai-org/GLM…

  16. comment
    Comment #48243628

    And their disk-based caching is amazing. I got a long 700k context session spanning more than a week, with pauses in between that was longer than a day, and some rewinds mixed in a…

  17. comment
    Comment #48145419

    Hah, that's because the prompt itself was only about 30 tokens. We need a much bigger prompt to properly test PP.

  18. comment
    Comment #47916712

    Huh that's not what I gathered from the tweet at all. If I am going to write a five why's analysis, the immediate cause is the LLM wrongly decided to delete a volume, while the roo…

  19. comment
    Comment #47915102

    If I understand correctly, both the staging database and the production database share the same volume. Thus, production data was gone as well after deleting the volume. 1st hint -…

  20. comment
    Comment #47882623

    Should be about 10~20 GiB per session. Save/restore is exactly what DeepSeek does using its 3FS distributed filesystem: https://github.com/deepseek-ai/3fs#3-kvcache With this much …

  21. comment
    Comment #47800594

    Based on the release schedule of 3.5 previously, my optimistic take is that they distill the small models from the 397B, and it is much faster to distill a sparse A3B model. Hopefu…

  22. comment
    Comment #47786670

    His Vibe Coding book is invaluable as a textbook example of slop.

  23. comment
    Comment #47740856

    https://github.com/anthropics/claude-code/issues/46829#issue... - Have you checked with your colleague? (and his AI, of course)

  24. comment
    Comment #47713368

    > EC2 instances on shared hardware showed up to 30% variance between runs due to noisy neighbors. Based on this finding, I suppose the better way is to rely on local hardware whene…

  25. comment
    Comment #47713094

    Very nice TG improvement from Flash Attention KQ fusion. Is it something that was already done in ik_llama.cpp? If not, then it will be a welcomed addition for hybrid CPU/GPU infer…