Live data from Hacker News

Viewing profile — chaotic-good

chaotic-good

HN member
Joined
Mon, Aug 12, 2013, 11:53 AM UTC
HN karma
182
Public activity
108 items

About chaotic-good

No profile information was provided.

Recent public activity

  1. comment
    Comment #46147374

    I don't see any mentions of p99 latency in the benchmark results. Pushing gigabytes per second is not that difficult on modern hardware. Doing so with reasonable latency is what's …

  2. comment
    Comment #43362219

    I tend to agree with this. The code tend to be loaded with primitives that express ownership semantics or error handling. Every time something changes (for instance, you want not j…

  3. comment
    Comment #37051139

    I'm not asking anything on behalf of any company and just genuinely curious (and I don't think that we're competitors, both systems are designed for totally different niches). I'm …

  4. comment
    Comment #37049877

    > Why replicate data at the VM/disk level when those disks are already provided as a fully redundant system? That's easy. EBS and similar solutions comes with the price. They're ve…

  5. comment
    Comment #37049036

    It could be easy to operate when everything is fine but what's about incidents? If I understand correctly, there is a metadata database (BTW, is it multi-AZ as well?). But what if …

  6. comment
    Comment #35974430

    The disk thrashes because of fsyncs (Kafka doesn't perform any fsync's). But you can provision more disk space to mitigate this problem. And it looks like the test was set up this …

  7. comment
    Comment #35974405

    You have to provision you disk space accordingly. NVMe needs some free space to have good performance. In this case I think that in Redpanda benchmarks the disk space was available…

  8. story
  9. story
  10. comment
    Comment #18411699

    Modern TSDB is expected to support tags. This means that every series will have a unique set of tag-value pairs associated with it. E.g. 'host=Foo OS=CentOS arch=amd64 ssdmodel=Int…

  11. comment
    Comment #18404539

    90% compression on time series is not viable unless you have some very specific dataset.

  12. comment
    Comment #18404506

    'metric_name text' is actually a tag-value list. Many TSDB's allows you to match data by tag. Each tag should be represented by a column in your example. Single table design will b…

  13. comment
    Comment #18404257

    They can't handle high cardinality. Imagine having millions of columns in the column-oriented database (70% of those columns are updated every second). Imagine that you have to add…

  14. story
  15. story
  16. story
  17. story
  18. comment
    Comment #14551600

    > Successful, popular concurrent platforms like Erlang/OTP, Nginx, and node.js, eschew threads in favor a single-threaded, async/non-blocking code model. All these platforms have s…

  19. comment
    Comment #14418361

    Yes, it was possible for a long time.

  20. comment
    Comment #14348208

    It's not a TSDB. It doesn't support ingestion without some fancy batching. The insert rate will be too limited without that. MergeTree was designed for batch processing, not for re…

  21. comment
    Comment #14347976

    JFK that the link doesn't work: the Russian government is going to create national big data operator. All internet companies must store their information there. They can use this i…

  22. story
  23. comment
    Comment #14250432

    What do you mean by gloss?

  24. comment
    Comment #14250296

    If I understand this right, with Intel's Optane you will eventually need to write everything to HDD because data collection happens at steady pace and the cache size is limited.

  25. comment
    Comment #14250110

    >> Maybe I'm getting this all wrong, but aren't the leaves also representing chunked data, which is compressed. Leaf nodes contain data from one series (this data should be read to…