If you change then will anything limit the peak degree of parallelism? The worker pool size is such a limiting factor. May be important for you. If so, plan another throttling mechanism.
On Fri, Jul 3, 2020 at 7:03 AM Atakan Çolak <[email protected]> wrote: > Hiya everyone, > > I have a simple processor function that takes in data, processes it, and > sends it to a fellow goroutine which will eventually write them to DB. My > main concern is just to maximise current task/sec with a hard limit on CPU > usage. Currently I'm using a worker pool model that share a task channel to > receive their tasks. I think another alternative solution could be setting > GOMAXPROCS and generate a new goroutine for each task, as Go is able to > handle thousands of goroutines easily. I wanted to ask about ups and down > of both of these approaches. > > Thank you. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/567ff4bd-a99e-4af5-bd46-7859d98575cbo%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/567ff4bd-a99e-4af5-bd46-7859d98575cbo%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- *Michael T. [email protected] <[email protected]>* -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CALoEmQx4Wf5Czs8LmR2caOTYT5vVNZpzWNn0Yj6aUhhR9RHmFw%40mail.gmail.com.
