On Tue, May 2, 2017 at 2:43 AM, Nikos Anastopoulos 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
Τη Κυριακή, 30 Απριλίου 2017 - 2:36:15 π.μ. UTC+3, ο χρήστης Ian Lance
Taylor έγραψε:
>
> On Sat, Apr 29, 2017 at 3:09 AM, Nikos Anastopoulos > wrote:
> > Τη Σάββατο, 29 Απριλίου 2017 - 7:33:00 π.μ. UTC+3, ο χρήστης Nikos
> > Anastopoulos έγραψε:
> >>
> >> Either
On Sat, Apr 29, 2017 at 3:09 AM, Nikos Anastopoulos wrote:
> Τη Σάββατο, 29 Απριλίου 2017 - 7:33:00 π.μ. UTC+3, ο χρήστης Nikos
> Anastopoulos έγραψε:
>>
>> Either through the /proc/PID/tasks entries, or using
>> GODEBUG=schedtrace=1000.I get consistent results with both ways
Τη Σάββατο, 29 Απριλίου 2017 - 7:33:00 π.μ. UTC+3, ο χρήστης Nikos
Anastopoulos έγραψε:
>
> Either through the /proc/PID/tasks entries, or using
> GODEBUG=schedtrace=1000.I get consistent results with both ways
With some experimentation more I did, I tend to believe this behavior has
somehow
Either through the /proc/PID/tasks entries, or using GODEBUG=schedtrace=1000.I
get consistent results with both ways
--
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
On Thu, Apr 27, 2017 at 4:47 AM, Nikos Anastopoulos wrote:
>
> I have a Go app that, among others, continuously parses XML files to extract
> dynamic info. This seems to cause a strange behavior in the Go runtime,
> according to which the underlying Go threads keep increasing