[Golang] Mutual exclusion in the end who do? Channel or mutex?

Source: Internet
Author: User
This is a created article in which the information may have evolved or changed. Channel
– Essentially a MessageQueue
– Very Orthodox implementation of inter-body communication facilities
sync. Mutex/rwmutex/cond/etc
– Do not treat the channel as a balm, the Mutex is still

• Myths
– Use channel for mutual exclusion (normal should let mutex do)
• For example, multiple Goroutine access a set of shared variables
Channel Cost – as a message queue, the channel cost is higher than the Mutex
– Where is the cost?
Channel has a Mutex inside it because it belongs to a shared variable.
There may be Cond inside the channel to wait or wake up the condition
Goroutine
• Assign the CPU and let another goroutine get execution opportunity, this cut
The replacement period is much higher than the cost of the Mutex to check the competitive state (the latter is usually
Just an atomic operation)
Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.