N in this case will be similar to the value of GOMAXPROCS, on the assumption that scaling that far pays off.
I would love to have the problem of having a 128 core computer…. (Though then if scaling tops out at 32 cores one simply runs 4 experiments..) — P > On Jan 13, 2021, at 10:31 PM, Robert Engels <reng...@ix.netcom.com> wrote: > > I forgot. But it’s to important to mention that different synchronization > methods perform differently under contention so what works well for 2 might > be really poor with 64. > >> On Jan 13, 2021, at 10:04 PM, Kurtis Rader <kra...@skepticism.us> wrote: >> >> >> On Wed, Jan 13, 2021 at 7:58 PM Robert Engels <reng...@ix.netcom.com >> <mailto:reng...@ix.netcom.com>> wrote: >> Why limit yourself to two? Use N routines and have each process every N in >> the list. >> >> You missed this statement in the original message of this thread: >> >> So the sketch of the go implementation is that I would have three threads - >> main, t0, and t1. (more for a real system, but two suffices for explanation) >> >> They were deliberately simplifying the problem to eliminate irrelevancies. >> Such as the number of CPU cores available; although, they did assume at >> least two cores :-) >> >> -- >> Kurtis Rader >> Caretaker of the exceptional canines Junior and Hank > > -- > You received this message because you are subscribed to a topic in the Google > Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/yqxfGIGDKr4/unsubscribe > <https://groups.google.com/d/topic/golang-nuts/yqxfGIGDKr4/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com > <mailto:golang-nuts+unsubscr...@googlegroups.com>. 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/08536531-8882-40BD-9F75-1B5A63BDF8CF%40bsc.es.
