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 <yunthana...@gmail.com> 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 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 op/s, it drops > to nearly > 7,000,000 op/s in golang's implementation. ) > > On Mon, Sep 18, 2017 at 5:28 AM, David Collier-Brown <davecb...@gmail.com> > wrote: > >> You may need to look and see what __vdso_clock_gettime_sym calls at the >> system-call level, and compare that with the system calls reported by >> strace from your executable. >> >> I assume you want some particular thing that __vdso_clock_gettime_sym >> does: try asking the folks about *that*, as they may already know. >> >> -- >> 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. >> > > -- 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.
