On Tue, May 2, 2017 at 2:43 AM, Nikos Anastopoulos <n.anas...@gmail.com> wrote: > > Thanks for your feedback. As a last question, what is the application > aspect (or other factors) that determines how quickly new threads are being > employed over time? For example, in my scenario above, if I choose to do the > parsing using plain regexp rather than xml.Unmarshal, the threads will reach > a count of ~8 within the same period (4 mins), vs 28 when using > xml.Unmarshal. In some other Go apps, threads will remain constant (i.e., 4) > forever. Where is this difference attributed?
I don't know that there is any one thing. I would expect to be based primarily on how many different goroutines are started and how often those goroutines block in a system call. In general the Go runtime does not try to limit threads to less than GOMAXPROCS. Ian -- 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.
