Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: zhenyu.ren@aliyun.com (zhenyu.ren)
Subject: [lttng-dev] UST performance
Date: Mon, 27 Apr 2015 11:01:12 +0800	[thread overview]
Message-ID: <2d399e36-59c3-4648-8b13-53a4b36b68de@aliyun.com> (raw)

Hi,dev? ? About a month ago,I asked a question about how to do time recording for ust event when vdso_clock_gettime not availble on my platform?Glibc too old?.Recently I implemented a lib to analyze vdso in memory and lookuped the symbol vdso_clock_gettime successfully.With this vdso_clock_gettime availble,I get a 16% improvement in time spending per ust event. I.E. I measured the time taked by a event with 10 bytes string :?no ? vdso_clock_gettime : 0.642us?with vdso_clock_gettime?0.554usHowever?Both the numbers are much higher than the following 0.28us(But closed to 0.5us --W/O opt). So what's the difference between UST(0.28us) and UST W/O OPT(0.5us)???PS:My hardware2 x Xeon E5-2430 ?2.20GHz 100MHz FSB (24 cores)?94.6GB / 96GB 1333MHz DDR3 == 6 x 16GB, 6 x emptyThankszhenyu.ren

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150427/c43822fb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: temp4cj.png
Type: application/octet-stream
Size: 34762 bytes
Desc: not available
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20150427/c43822fb/attachment-0001.obj>


             reply	other threads:[~2015-04-27  3:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  3:01 zhenyu.ren [this message]
2015-04-28 15:47 ` Mathieu Desnoyers
2015-04-29  1:31 ` [lttng-dev] 答复: " zhenyu.ren
2015-04-29  2:25   ` Mathieu Desnoyers
2015-04-29  3:39   ` [lttng-dev] 答复:答复: " zhenyu.ren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2d399e36-59c3-4648-8b13-53a4b36b68de@aliyun.com \
    --to=zhenyu.ren@aliyun.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox