From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, T_KAM_HTML_FONT_INVALID,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 04304C4363A for ; Mon, 5 Oct 2020 22:18:05 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DB3AF206CB for ; Mon, 5 Oct 2020 22:18:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b="WIPBLz5g" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DB3AF206CB Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4C4pRY6PRDzDrRv for ; Tue, 6 Oct 2020 05:05:29 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=google.com (client-ip=2607:f8b0:4864:20::b2b; helo=mail-yb1-xb2b.google.com; envelope-from=pashag@google.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=reject dis=none) header.from=google.com Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4C4pQN2m5LzDqWj for ; Tue, 6 Oct 2020 05:04:22 +1100 (AEDT) Received: by mail-yb1-xb2b.google.com with SMTP id x8so7335527ybe.12 for ; Mon, 05 Oct 2020 11:04:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=9ew90SXu8kTTO99lFQ++FuIl22x4VvwSac3YCASvaqI=; b=WIPBLz5gkb/q7YvU3ILnMVBxcu+/E4Xx4nvOi+wU0e46trqv2JNfO9T9Q1cSktIH9d H+nSXnamkF7bWCafF5N8Czd93oRgH3bHMnAMBArB6dha2xmvhq7HcqMKbLqKrNk7VMtS +gnt6T3xb9vjwNFrB31/wNVUVYAjuI9z9f/U+CJQ7TdhW1uaSnC7y6mfEUGHPo1Zy/+q 4DUlL6YMMQV9D+FbDe7t0tndmW2Ql91nlkPlEpaJ1eqA3NlICeO7pjhsRS42J74x0vJg eUl36NUQEtZ74v3HvFn1+ih1SJcJOtwCdjs7aPkn/KUsMKJQ83lRjG7SkG2sXz9znILH L2HQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=9ew90SXu8kTTO99lFQ++FuIl22x4VvwSac3YCASvaqI=; b=mlC+FMO/R2Ag9c4WeXoQwvuh8KjZXay8Jx9NgKeck8+J7NOswjNSX04yxsfD41F2zd wH9l14Hy8GtPHEk0dBTJ7VN0IB0efP/Dg6whk1eIJOZJzf/IMqeXO08ScmS0AOvB3nfc Cfo3F+3g1yZbCL1CiEyORAujM/dfKA2KMyFZZSEPguV6zPWq9HniY9C5aJzsF/i2JIbi ZpMrCEwTUZ0dCSmOvvx0yjrKdvwxNG6Ic2tQMcbZery/pzggJbeYaFrmhO6TlT+jEXYM JBQtVCOgmSvqIcHoLIq1jclS7OpiW+A3iewffw//nGziw0QAADHHf6Y122R5EMDEAw1w q+OQ== X-Gm-Message-State: AOAM531OiMaBdBmeGO16zzseviNsU6pWx7HQlF8Ue1iGnVw7w6LL7TWA tVkC+Zifvc/XaP+k71vUgBsP7ljdqqQz0XkZklthTOK0NRGpOQ== X-Google-Smtp-Source: ABdhPJxKliKeWJc2sBjmU7WCrBvKHrKOJ+DobBtuTVJCcTYgejb2sPwoKP9RBGnMrWpgH+9a6JSagjOTu8JZvL/m+Zw= X-Received: by 2002:a9d:7095:: with SMTP id l21mr374683otj.224.1601920671332; Mon, 05 Oct 2020 10:57:51 -0700 (PDT) MIME-Version: 1.0 From: Pasha Ghabussi Date: Mon, 5 Oct 2020 13:57:41 -0400 Message-ID: Subject: BMC Performance Profiler To: openbmc@lists.ozlabs.org Content-Type: multipart/alternative; boundary="000000000000931b4205b0f038ce" X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Ed Tanous , Sui Chen , Ofer Yehielli Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" --000000000000931b4205b0f038ce Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello all, We would really appreciate it if you can take a few minutes to read the following proposal and let us know your thoughts and suggestions. We are developing a tool to investigate performance problems by looking at DBus traffic dumps. Current DBus inspection and visualization tools do not represent the DBus events similar to a typical performance profiler. Additionally, these tools do not address typical BMC workloads such as IPMI and ASIO. Hence, identifying potential performance problems requires inspecting the raw BMC DBus traffic, which can become a long and complex process. We want to add a graphical interface to webui-vue to visualize the DBus traffic to address the abovementioned problem. There have been DBus and IPMI performance-related discussions in the OpenBMC community, both of which can be helped by this work: IPMI-related issues started to appear as early as in 2017. One issue (#2630) describes a problem related to large numbers of sensors. Its follow-up (#3098) mentions =E2=80=9Chostboot= crashes due to poor IPMI performance=E2=80=9D. Another issue (#2519) describes a commonly-seen problem of IPMI taking very long to respond (> 5s). There are also discussions on RedFish performance on the mailing list; A patch optimized DBus performance by introducing a cache for name translation. All the performance investigations listed above involve DBus and may be helped by this work. We are planning to use the BMCweb file hosting functionality to access the DBus event dumps and visualize the events in the web UI. The available profiling tools such as dbus-pcap , Wireshark , Bustle , Snyh , or DFeet do not provide the exact functionality we are looking for. Our goal is to develop functionalities similar to other widely used profilers such as GPUView or VTune Profiler. One alternative solution considered was to stream DBus requests over websocket, but the existing websocket endpoints available on BMC webserver do not provide the exact information we need. Requirements and Scalability: - Should provide the adequate functionalities to filter, visualize the events timeline, and group the DBus traffic based on multiple criteria s= uch as type, source, destination, path, interface, demon signatures, and mor= e. - Should support capture of DBus messages using as little resources as possible. - Should be able to show many (~thousands of) entries on screen simultaneously - Integration with webui-vue Thank you --000000000000931b4205b0f038ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello all,

We would really appreciate it if you can take a few minutes to = read the following proposal and let us know your thoughts and suggestions.<= /span>

We = are developing a tool to investigate performance problems by looking at DBu= s traffic dumps. Current DBus inspection and visualization tools do not rep= resent the DBus events similar to a typical performance profiler. Additiona= lly, these tools do not address typical BMC workloads such as IPMI and ASIO= . Hence, identifying potential performance problems requires inspecting the= raw BMC DBus traffic, which can become a long and complex process. We want= to add a graphical interface to webui-vue to visualize the DBus traffic to= address the abovementioned problem.


There have been DBus and IPMI performa= nce-related discussions in the OpenBMC community, both of which can be help= ed by this work: IPMI-related issues started to appear as early as in 2017.= One issue (#2630) describes a problem related to l= arge numbers of sensors. Its follow-up (#3098) ment= ions =E2=80=9Chostboot crashes due to poor IPMI performance=E2=80=9D. Another issue (#2519) describes a commonly-seen problem = of IPMI taking very long to respond (> 5s).
There are also discussions on RedFish performance on the mailing lis= t; A patch optimized DBus perform= ance by introducing a cache for name translation.

All the performance investiga= tions listed above involve DBus and may be helped by this work.

<= br>

We are plan= ning to use the BMCweb file hosting functionality to access the DBus event = dumps and visualize the events in the web UI. The available profiling tools= such as dbus-pcap, Wireshark, Bustle, Snyh= , or DFeet do not provide t= he exact functionality we are looking for. Our goal is to develop functiona= lities similar to other widely used profilers such as GPUView or VTune Profiler.

One alternative solution = considered was to stream DBus requests over websocket, but the existing web= socket endpoints available on BMC webserver do not provide the exact inform= ation we need.


Requirements and Scalability:

  • Should provide the ade= quate functionalities to filter, visualize the events timeline, and group t= he DBus traffic based on multiple criteria such as type, source, destinatio= n, path, interface, demon signatures, and more.

  • =

    = Should support capture of DBus messages using as little resou= rces as possible.

  • Should be able t= o show many (~thousands of) entries on screen simultaneously

  • Integration with webui-vue

<= div>
Thank you
--000000000000931b4205b0f038ce--