Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
* [lttng-dev] UST performance
@ 2015-04-27  3:01 zhenyu.ren
  2015-04-28 15:47 ` Mathieu Desnoyers
  2015-04-29  1:31 ` [lttng-dev] 答复: " zhenyu.ren
  0 siblings, 2 replies; 5+ messages in thread
From: zhenyu.ren @ 2015-04-27  3:01 UTC (permalink / 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>


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2015-04-29  3:39 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-27  3:01 [lttng-dev] UST performance zhenyu.ren
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox