correction just to clarify in my previous mail : please read it as "around
34 go internal pthreads" instead of "around 34 goroutines"
Ian, the go internal pthreads left out after termination of all the
goroutines have the data (few strings allocated in application) as it is.
I am trying to mea
On Wed, May 6, 2020 at 10:02 AM Pavan wrote:
>
> Thanks Ian. I start some 20 go routines and each routine involves calling C
> functions and finally all go routines terminate. since each goroutine uses
> LockOSThread at the begining, all the pthreads spawned as part of goroutines
> exit too.
>
Thanks Ian. I start some 20 go routines and each routine involves calling C
functions and finally all go routines terminate. since each goroutine uses
LockOSThread at the begining, all the pthreads spawned as part of
goroutines exit too.
Now i see around 34 goroutines, few of them have stack s
On Fri, Apr 24, 2020 at 3:39 AM Pavan wrote:
>
> how do we terminate the go generated internal OS threads. I am debugging an
> issue , where RES(memory resdent size) size of. a process increases as
> goroutines used increases.
> Iam trying to reduce the threads footprint contribution of proce
Hi,
how do we terminate the go generated internal OS threads. I am debugging
an issue , where RES(memory resdent size) size of. a process increases as
goroutines used increases.
Iam trying to reduce the threads footprint contribution of process RES ,
hence. terminate the additional threads
