Re:The ups of downs of porting 50k lines of C++ to Go
by bjackman on Saturday March 07, 2015 @08:44AM
(#9161794)
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.
[ Parent
| on HN ]
Re:The ups of downs of porting 50k lines of C++ to Go
by iends on Saturday March 07, 2015 @10:08AM
(#9161938)
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/16Y4IsnNRCN43Mx0NZc5YXZLo...
Re:The ups of downs of porting 50k lines of C++ to Go
by _ak on Saturday March 07, 2015 @07:03PM
(#9163724)
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.
Re:The ups of downs of porting 50k lines of C++ to Go
by pron on Sunday March 08, 2015 @10:34AM
(#9165683)
Like the author's case, yours sound a much more appropriate choice of Java. Why have you picked Go?