Live data from Hacker News

Viewing profile — derekcollison

derekcollison

HN member
Joined
Fri, Feb 04, 2011, 5:10 PM UTC
HN karma
247
Public activity
22 items

About derekcollison

[ my public key: https://keybase.io/derekcollison; my proof: https://keybase.io/derekcollison/sigs/JVKLI7451s16UERM-2FfEGrl2b5_ngeUPHToVol3Y-w ]

Recent public activity

  1. comment
    Comment #45703989

    We are waiting on the IO abstraction for a supported Zig client (There are others though today), but this is specifically for a new initiative at Synadia that we will share more de…

  2. comment
    Comment #45703746

    TigerBeetle's excellent companion blog - https://tigerbeetle.com/blog/2025-10-25-synadia-and-tigerbee...

  3. story
  4. comment
    Comment #43798168

    Here is our official response. We also plan to have a public AMA early next week for anyone interested. https://www.synadia.com/blog/synadia-response-to-cncf

  5. comment
    Comment #32479294

    Would your company be willing to fund the development? Or would you be willing to post a PR? We would be happy to take a look.

  6. comment
    Comment #32478791

    We are waiting on demand for it. We have a bunch of folks using MQTT on NATS and NGS but no requests yet for MQTTv5 so far. Once we see legit demand we will make sure it's supporte…

  7. comment
    Comment #27977116

    We have some great work coming that allows lighter weight consumers to scale to that level and beyond. Happy to chat with folks on how we can make that work today.

  8. comment
    Comment #20564926

    We are always interested in feedback on how we can do better. Feel free to jump on our slack channel to join the community. We are actively working on the C client. Interested in m…

  9. story
  10. story
  11. comment
    Comment #11172017

    I think entropy, in however you measure it, does influence something like a UUID generator differently than the cryptographic algorithms. What you are trying to achieve, or more im…

  12. comment
    Comment #11171949

    I agree, was simply sharing because it was a need we had, which might be a need someone else had as well. Anyone can feel free to use it or not.

  13. comment
    Comment #11171011

    I disagree, either the entropy is drained and the randomness of what the pool returns (based on OS) is compromised or you get stalled waiting for more of it and decrease performanc…

  14. comment
    Comment #11170952

    Yes, but most UUID when moved across networks are translated to hex, so 32 bytes/characters whereas NUID's are 22 bytes, so generally a savings of 10 bytes per when stored as a str…

  15. comment
    Comment #11170399

    UUID V4 is ~900ns/op, NUID is ~60ns/op, so 15X speedup, or 1500%.

  16. comment
    Comment #8679055

    I am deeply saddened by this news. I remember trying to convince Ezra to join us to help out with CloudFoundry. I, like others, knew Ezra through the Ruby community where he was a …

  17. comment
    Comment #4887184

    The test is specific to a new NATS server written in GO (gnatsd). I described in more detail above the tests and what they do, but suffice it to say that it does test the message p…

  18. comment
    Comment #4887171

    It is not, but its on my TODO list, and I have also observed similar behavior at times. I have taken care to make sure the synchronization is efficient, but running the test is nee…

  19. comment
    Comment #4887157

    It is not one big write, but optimizations around msgs/write using buffering are used in clients, with obvious care to balance latency and throughput. In the benchmark, the write b…

  20. comment
    Comment #4887133

    That is correct, I am only attempting to measure the efficiency of the messaging processing engine within the server. I did want to include the network stack and the buffering port…

  21. comment
    Comment #4887116

    The simple benchmark is testing throughput of a messaging system, specifically a new server written in Go. Both the client and server are on the same machine, but going over a tcp/…

  22. comment
    Comment #2460561

    We plan on doing that, appreciate the feedback.