[go-nuts] Re: How to Optimize A Golang Application Which Has More Than 100 Million Objects at Peak?

Thanks a lot. You are so kind and nice :-D I tried golang's heap profile and it is very very helpful. By the way, what do you think about this article: https://dgraph.io/blog/post/manual-memory-management-golang-jemalloc/ 在2021年7月18日星期日 UTC+8 下午11:27:38 写道： > Two other replies have menti

Re: [go-nuts] `ltrace` yields "Couldn't find .dynsym or .dynstr in "/proc/*/exe" with binaries generated by "go build *.go"

rmat will be modified in the future. On Mon, Sep 18, 2017 at 5:47 PM, Konstantin Khomoutov wrote: > On Sat, Sep 16, 2017 at 04:51:00AM +0800, Sen Han wrote: > > Thanks for your information. I want to use `ltrace` to find out if the > > golang binary is using > > the __vdso_cl

Re: [go-nuts] Re: `ltrace` yields "Couldn't find .dynsym or .dynstr in "/proc/*/exe" with binaries generated by "go build *.go"

Which in this case, the `strace` cannot trace a single syscall that involves the time. On Mon, Sep 18, 2017 at 7:08 AM, Sen Han wrote: > In `go1.9 @ linux 3.10.0-327.el7.x86_64`, the call __vdso_clock_gettime_sym > is > completely in userspace, and does not involve any syscall in t

Re: [go-nuts] Re: `ltrace` yields "Couldn't find .dynsym or .dynstr in "/proc/*/exe" with binaries generated by "go build *.go"

In `go1.9 @ linux 3.10.0-327.el7.x86_64`, the call __vdso_clock_gettime_sym is completely in userspace, and does not involve any syscall in the kernel, and that is the reason __vdso_clock_gettime_sym with CLOCK_MONOTONIC is so fast. ( In C, the perf of __vdso_clock_gettime_sym is about 14,000,000 o

Re: [go-nuts] Latency profiling

(Sorry for the noise.) Hi Juliusz, this tool go-tool-trace-greediest-goroutines would be helpful.( may also refer the issue 20792 ) All best -- Sen On Sun, Sep 17, 2017 at 9:12 PM, Juliusz Chr

Re: [go-nuts] `ltrace` yields "Couldn't find .dynsym or .dynstr in "/proc/*/exe" with binaries generated by "go build *.go"

Thanks for your information. I want to use `ltrace` to find out if the golang binary is using the __vdso_clock_gettime_sym with CLOCK_MONOTONIC option for measuring time interval. But it finally turns out currently the `ltrace` cannot works very well with go built binaries on vdso tracing. Is the

Re: [go-nuts] Go's scheduler always “stuck” after certain time when executing the code below

r just let the other several goroutines which is already pending all switch to the 4 left idly goroutine 'slots' and run on instead of suspend forever? I think there is probably some design flaw about it. On Wed, Jun 21, 2017 at 10:18 PM, Sen Han wrote: > > just add a function ca

Re: [go-nuts] Re: Go's scheduler always “stuck” after certain time when executing the code below

> > This piece of code prohibits cooperative scheduling in 599 999 999 out of 600 000 000 times. It's a nice example how to not code in Go. Thanks Jan for your reply :) > Particularly, delays should be implemented using the functions in the time package, not by burning CPU cycles at the expen