|| at Apr 30, 2014 at 9:24 am
On Wednesday, 30 April 2014 09:32:09 UTC+1, dja...@gmail.com wrote:
is there are reason to mange pool of running goroutines ?
Pools are useful for when you need to bound the number of running
goroutines. They can also help with latency, since there's less chance of
starvation (where the number of goroutines is bounded).
use case is network server that receive requests and launch goroutines (
short lived ) to handle requests.
Since goroutines are cheap, they lend well to being (relatively)
does goroutines generate garbage ?
Afaik they don't generate garbage in of themselves, just allocating 8kb of
stack space. This isn't garbage collected in the traditional sense though.http://golang.org/doc/faq#goroutines
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 firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.