[go-nuts] Re: locking memory pages

2017 г., 0:18:50 UTC+3 пользователь Ganesh Sangle > написал: >> >> We have written a server in golang, and the requirement is that this >> server should be as responsive and the process should never be swapped out. >> To enable this we added: >> err = syscall.M

[go-nuts] locking memory pages

We have written a server in golang, and the requirement is that this server should be as responsive and the process should never be swapped out. To enable this we added: err = syscall.Mlockall(syscall.MCL_CURRENT | syscall.MCL_FUTURE) The resulting behavior seems that top shows RES memory always

[go-nuts] Re: too many runtime.gcBgMarkStartWorkers ?

Thanks Dave, we do set the GOMAXPROCS to 64. thanks for explanation. On Wednesday, December 28, 2016 at 12:06:42 AM UTC-8, Ganesh Sangle wrote: > > Hi, > While examining the stack trace from a crash where the process seems to > have become extremely slow, I see a lot of thes

[go-nuts] too many runtime.gcBgMarkStartWorkers ?

Hi, While examining the stack trace from a crash where the process seems to have become extremely slow, I see a lot of these goroutines: goroutine 66 [mark worker (idle)]: runtime.gopark(0x2cf6cf0, 0xc820d1, 0x29268b0, 0x12, 0x14, 0x0) /usr/local/go/src/runtime/proc.go:185 +0x163 fp=0

[go-nuts] understanding go stack trace

I have a go process which has several go-routines, and these go-routines are suppose to run every few seconds. If not, they print a message that they are not being scheduled as requested and abort the program. For example, on go routine prints something, sleeps for two seconds, and repeats this