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> 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 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/D17BA55A-2BD5-43A6-9BB1-38AF6E90E880%40ix.netcom.com.
