This is a created article in which the information may have evolved or changed.
The advantages of the Go language:
concurrency/network/performance/tools (Fmt/pprof/test)/Standard library (http/json/log/flags/atomic)/google
The true fatal flaw of the Go language garbage collector is that it can cause unpredictable intermittent pauses throughout the process. Like some large background service programs, such as game servers, app containers, due to large memory, the number of memory objects, GC to complete a recovery cycle, may take a few seconds or longer, during this time, the entire service process is blocked, paused, in the external view is service interruption, no response, The more awesome concurrency mechanism is here to fail. The garbage collector starts on a regular basis and causes a short service outage every time it is started, does anyone else dare to use it? This is a background server process, which is the key application area of Go language.
More Disadvantages: http://blog.csdn.net/liigo/article/details/23699459
http://www.csdn.net/article/2014-11-07/2822545
During the development of Xiaomi's second edition snapping system, we encountered an excessive memory consumption problem with the HTTP layer Go program. Because the HTTP layer is primarily used to maintain the user's access requests, the data in each request consumes a certain amount of memory, and when a large number of users access it, the memory usage is increased. When memory consumption reaches a certain level (50%), the GC mechanism in GO is getting slower, but there will still be a large number of users to access, resulting in an "avalanche" effect, the memory is rising, the final machine memory utilization will reach more than 90% or even 99%, resulting in service unavailability. To avoid the "avalanche effect" when the GC mechanism in the go language is not optimized, it is necessary to avoid exceeding the limit (50%) of the memory consumed by the service, and the GC can be effective when it is within this limit. You can spread the memory pressure by increasing the server, and try to optimize the memory size that the service consumes.
Http://www.oschina.net/news/58619/go-1-5-bootstrap-plan?p=3#comments