Live data from Hacker News

Viewing profile — dzr0001

dzr0001

HN member
Joined
Fri, May 22, 2020, 3:46 AM UTC
HN karma
5
Public activity
10 items

About dzr0001

No profile information was provided.

Recent public activity

  1. comment
    Comment #48394147

    And making TLS more difficult, especially for HA systems. Guess you would just need one cert for 127.0.0.1 for all local services.

  2. comment
    Comment #48213045

    My token throughput is much better using vLLM-mlx on my M2 ultra than llama.cpp. It might be worth a shot to give it a try.

  3. comment
    Comment #46798292

    I think there's a fundamental difference between programming language repos and package repositories like the official RPM, deb, and ports trees. These (typically) operating system…

  4. comment
    Comment #44786774

    I suspect that there's some marketing component at play here. People who do not own but observe devices making seemingly unnecessary noises might perceive these devices as premium.…

  5. comment
    Comment #44042958

    I did a quick scan of the repo and didn't see any reference to Ray. Would this indicate that llm-d lacks support for pipeline parallelism?

  6. comment
    Comment #43407037

    It does if you need pipeline parallelism across multiple nodes.

  7. comment
    Comment #43359542

    Unfortunately, this data is harder to find than it should be. For instance, just looking at Kioxia, which I've found to be very performant, their datasheets for the CD series drive…

  8. comment
    Comment #43356378

    What drive is this and does it need a trim? Not all NVMe devices are created equal, especially in consumer drives. In a previous role I was responsible for qualifying drives. Any d…

  9. comment
    Comment #38888555

    I have the original M1 air that I got the day it released in 2020. In a typical week, I will let my battery discharge to less than 10% twice and recharge it to 100%. I've logged 45…

  10. comment
    Comment #23268489

    We used to have a pub rate of about 200k msgs/s, from about 400 producers all to a single exchange and had similar issues. However, we were able to mitigate this by using lazy queu…