4 ms·

Wow, 400-500ms pauses? Is that the case in newer Go versions as well? Seems like that would wipe out viability for a whole load of applications.

• iends 12y ago
  Go is actively working on this. Go 1.5 will have concurrent GC and is shooting to stop the world for only 10ms. You can read more here: https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLovrHvvLhK_h0KN8woTO4/edit https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLo...
• _ak 12y ago
  Not really. If you manage your allocations properly, you will never have such long GC pauses. N.B. we use Go for real-time bidding (in the context of programmatic buying of ad space), and can easily respond to 6000 QPS on a single server within a 100ms time frame (from the SSP's POV), with a working set of about 2-3 GB that we constantly keep in memory.
  • chupy 12y ago
    That sounds really nice, but how often does that working set change?
  • pron 12y ago
    Like the author's case, yours sound a much more appropriate choice of Java. Why have you picked Go?
    • apta 12y ago
      Probably hype. There is a lot of hype in the industry, unfortunately.