Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] major variations in perfomance figures
Date: Fri, 3 Apr 2015 11:21:05 -0400	[thread overview]
Message-ID: <CA+jJMxuOT-zRW4k74C-gD3n4XP3mWO4HGYCLu=LT+EnMuRncAQ@mail.gmail.com> (raw)
In-Reply-To: <trinity-44577199-4bb4-4bf1-8595-785637f25968-1428072450572@3capp-gmx-bs60>

On Fri, Apr 3, 2015 at 10:47 AM, Wolfgang Rostek <wolfgang.rostek at gmx.de> wrote:
> Hi J?r?mie,
>
> thanks for your feedback.
>
> I've added only a loop to the end of the demo programm.
>
> Frequence scaling I can't imagine on my dektop machine.
> It is a jump between 350ns and 800ns. In the loop below
> all the events of one test run are of equal time distance,
> either slow or fast.

Frequency scaling can still definitely play a role, even on a desktop machine.
Also, Core i5 chips support Turbo Boost which should be disabled to
perform benchmarks.

I'm guessing you get your time measurements from the timestamps in the
trace?

J?r?mie

>
> Wolfgang R.
>
>
> https://github.com/lttng/lttng-ust/blob/master/doc/examples/demo/demo.c
> ...
> tracepoint(ust_tests_demo, starting, 123);
> for (i = 0; i < 5; i++) {
> netint = htonl(i);
> tracepoint(ust_tests_demo2, loop, i, netint, values,
> text, strlen(text), dbl, flt);
> }
> tracepoint(ust_tests_demo, done, 456);
> tracepoint(ust_tests_demo3, done, 42);
>
> for (i = 0; i < 300; i++) {
> if(i % 10 == 0) {
> tracepoint(ust_tests_demo, done, i);         <=========
> }
> }
>
> fprintf(stderr, " done.\n");
> return 0;
> }
>
>> Gesendet: Freitag, 03. April 2015 um 16:22 Uhr
>> Von: "J?r?mie Galarneau" <jeremie.galarneau at efficios.com>
>> An: "Wolfgang Rostek" <wolfgang.rostek at gmx.de>
>> Cc: "lttng-dev at lists.lttng.org" <lttng-dev at lists.lttng.org>
>> Betreff: Re: [lttng-dev] major variations in perfomance figures
>>
>> On Tue, Mar 31, 2015 at 3:46 PM, Wolfgang Rostek <wolfgang.rostek at gmx.de> wrote:
>> > Hi all,
>> >
>> > I did a first perfomance test extending the demo example
>> > by tracing 30 simple integers in a loop.
>> >
>> > For a similar CPU (i5 quad core 2.8GHz) I saw values
>> > mentioned around 250ns in the forum.
>> >
>> > I've tried the test several time and could come down
>> > to about 350ns. The machine was almost idle for all
>> > tests.
>> >
>> > What makes me wonder is a large variation with frequent
>> > runs giving me 750-800ns.
>> >
>> > Not the absolute time but the variations isn't clear
>> > to me. From my understanding the caller path is more
>> > or less straight to shared memory. Why do different
>> > runs show more than double the time for the traces?
>>
>> Good question. Can you share the benchmark's code?
>> Also, make sure frequency scaling is disabled on your system; it could
>> explain these kinds of variations.
>>
>> J?r?mie
>>
>> >
>> > Wolfgang R.
>> >
>> >
>> >
>> > _______________________________________________
>> > lttng-dev mailing list
>> > lttng-dev at lists.lttng.org
>> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>
>>
>>
>> --
>> J?r?mie Galarneau
>> EfficiOS Inc.
>> http://www.efficios.com
>>



-- 
J?r?mie Galarneau
EfficiOS Inc.
http://www.efficios.com



  reply	other threads:[~2015-04-03 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <trinity-1e9921b3-666b-4656-bcb8-a2125944698f-1427831168919@3capp-gmx-bs39>
2015-04-03 14:22 ` Jérémie Galarneau
2015-04-03 14:47   ` Wolfgang Rostek
2015-04-03 15:21     ` Jérémie Galarneau [this message]
2015-04-03 15:34       ` Wolfgang Rostek
2015-04-03 16:49 Jesper Derehag

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='CA+jJMxuOT-zRW4k74C-gD3n4XP3mWO4HGYCLu=LT+EnMuRncAQ@mail.gmail.com' \
    --to=jeremie.galarneau@efficios.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