having workers pull from a single queue is an excellent approach. (unless you pull more than 3 million items per second from that queue :-)
On Fri, Nov 24, 2017 at 2:11 AM, roger peppe <rogpe...@gmail.com> wrote: > On 24 November 2017 at 05:46, <carsten.orthba...@gmail.com> wrote: > > Hi! > > > > This should be covered somewhere already but I can't find it. So here's > my > > question: > > > > Assume N workers running in a goroutine each and a number of Job tasks > > coming in. > > > > The consensus appears to be to have one dispatcher goroutine collecting > all > > jobs, then pulling a ready worker from a single queue of worker channels. > > What do you base that consensus on? Having all workers pull from > a single shared channel seems like a fine way to do things. > > It would help if you could provide some more complete code - the > snippets you provided don't really make sense on their own to me. > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- Michael T. Jones michael.jo...@gmail.com -- 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. For more options, visit https://groups.google.com/d/optout.
