Re: [go-nuts] Worker Pool vs. New Goroutine For Each Task

[Atakan Çolak]

Thank you, perhaps two cases are quite equivalent when used with 
semaphores. 

3 Temmuz 2020 Cuma 18:29:41 UTC+3 tarihinde Andrei Tudor Călin yazdı:
>
> Check out Bryan's talk[0], in particular from ~27:00 onward, where worker 
> pools are discussed. I highly recommend the entire talk.
>
> [0] https://www.youtube.com/watch?v=5zXAHh5tJqQ
>
> On Fri, Jul 3, 2020 at 5:03 PM Atakan Çolak  > 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 golan...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/golang-nuts/567ff4bd-a99e-4af5-bd46-7859d98575cbo%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Andrei Călin
>

-- 
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/8e2eccc0-73dd-4020-ab3d-a5575b5d4e8do%40googlegroups.com.

Re: [go-nuts] Worker Pool vs. New Goroutine For Each Task

[Andrei Tudor Călin]

Check out Bryan's talk[0], in particular from ~27:00 onward, where worker
pools are discussed. I highly recommend the entire talk.

[0] https://www.youtube.com/watch?v=5zXAHh5tJqQ

On Fri, Jul 3, 2020 at 5:03 PM Atakan Çolak 
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 golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/567ff4bd-a99e-4af5-bd46-7859d98575cbo%40googlegroups.com
> 
> .
>


-- 
Andrei Călin

-- 
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/CANnvmN5zQjYLMjLEhi_oUDJzegCdiPUfuR5ET00zB7BN9dA_4w%40mail.gmail.com.

Re: [go-nuts] Worker Pool vs. New Goroutine For Each Task

[Michael Jones]

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 
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 golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/567ff4bd-a99e-4af5-bd46-7859d98575cbo%40googlegroups.com
> 
> .
>


-- 

*Michael T. jonesmichael.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CALoEmQx4Wf5Czs8LmR2caOTYT5vVNZpzWNn0Yj6aUhhR9RHmFw%40mail.gmail.com.

[go-nuts] Worker Pool vs. New Goroutine For Each Task

[Atakan Çolak]

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 golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/567ff4bd-a99e-4af5-bd46-7859d98575cbo%40googlegroups.com.