3 ms·

Happy to see it's written in Golang.

• bojo 12y ago
  As a Go developer I was happy as well. On the other hand this question immediately popped into my mind: What kind of overhead does the GC incur, and how does it affect processes like a database where low latency is desired?
  • datashovel 12y ago
    If I had to guess, I would say network and disk I/O will be the bottlenecks. Disk I/O less so because distributed system, and SSD. I imagine if anyone can solve GC issues, though, I would bet on Google :)
    • natebrennand 12y ago
      Their chosen solutions to the GC issues are in this roadmap. [0] [0]: https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLovrHvvLhK_h0KN8woTO4/preview?sle=true https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLo...
  • ansible 12y ago
    What kind of overhead does the GC incur, and how does it affect processes like a database where low latency is desired? The eventual goal (golang v1.5 IIRC) is to have 40ms out of every 50ms available for actual processing. This is the kind of 'soft real time' that should provide good responsiveness for most clients most of the time.