I have decided to believe that scheduling overhead is minimal, and only customize if this is untrue for my workload. [I don’t like customizing. Stuff in the standard library has been built by folk who have done this in anger, and the results have been widely used; plus principle of least surprise.] Thanks!
— P > On Jan 13, 2021, at 7:16 PM, Robert Engels <reng...@ix.netcom.com> wrote: > > This https://github.com/robaho/go-concurrency-test > <https://github.com/robaho/go-concurrency-test> might help. It has some > relative performance metrics of some sync primitives. In general though Go > uses “fibers” which don’t match up well with busy loops - and the scheduling > overhead can be minimal. > WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer http://bsc.es/disclaimer -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/C9D511FC-128F-429E-8D5B-CF15811A9C66%40bsc.es.
