Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: a.aleksandrov@yadro.com (Aleksander Aleksandrov)
Subject: [lttng-dev] Babeltrace 2.0.2 performance issue
Date: Thu, 2 Apr 2020 16:32:03 +0000	[thread overview]
Message-ID: <a095fcdafcf24edf85e047e9c177b0d0@yadro.com> (raw)
In-Reply-To: <e21e3ce3-0180-7aa7-aa16-9e889b69269b@efficios.com>

Hi Simon,


Thank you for your message! Unfortunately, I missed your previous message, sorry for this.


I processed the CI's trace logs, I got the following performance: bt2 (140.51s) vs bt1 (122.00s). In my opinion, the values are quite similar comparing with my other measurements.


Best regards,

Aleksandr


On 2020-03-13 4:58 p.m., Simon Marchi wrote:
> Hi Aleksander,
>
> I just noticed you did not send your original email to the lttng-dev mailing list,
> please send such request on that mailing list, as it's of public interest:
>
>   https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
> See my previous response here:
>
>   https://pastebin.com/raw/3Q5PbYXn
>
> Simon
>

Hi Aleksander,

Sorry, I forgot to follow up.  Did you get my last message?

This is the trace we use for benchmarking: https://files.efficios.com/s/pog5raGkBkH63y9

Could you try to compare bt1 and bt2 using that trace?

On the CI benchmark system, we get some similar performance with both bt1 and bt2.  Although
a colleague tried on a recent AMD Ryzen 3700X CPU, and he says bt2 is slower than bt1 for
him (36s vs 33s).  I'd be curious to know what kind of numbers you get.

Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20200402/b10f6dce/attachment.htm>


  parent reply	other threads:[~2020-04-02 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <76e78e538b804aa2b78f320510e8c10d@yadro.com>
2020-04-02 16:30 ` Aleksander Aleksandrov
     [not found] ` <9ee46aeb-1b9b-c7d4-94ea-c15772bc05eb@efficios.com>
     [not found]   ` <5f3249fe30e040b5b4a444fba495de62@yadro.com>
     [not found]     ` <6992879d-d139-06f5-d325-02530ad2c1b1@efficios.com>
     [not found]       ` <e21e3ce3-0180-7aa7-aa16-9e889b69269b@efficios.com>
2020-04-02 16:32         ` Aleksander Aleksandrov [this message]
2020-04-02 16:53           ` Jonathan Rajotte-Julien

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=a095fcdafcf24edf85e047e9c177b0d0@yadro.com \
    --to=a.aleksandrov@yadro.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