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=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, T_KAM_HTML_FONT_INVALID,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL 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 E4C39C433E7 for ; Thu, 8 Oct 2020 21:46:43 +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 96E9122241 for ; Thu, 8 Oct 2020 21:46:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="J3YMMkZV" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 96E9122241 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 4C6lCM4h9lzDqWx for ; Fri, 9 Oct 2020 08:46:39 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=google.com (client-ip=2607:f8b0:4864:20::330; helo=mail-ot1-x330.google.com; envelope-from=pashag@google.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20161025 header.b=J3YMMkZV; dkim-atps=neutral Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 4C6l951cK8zDqX6 for ; Fri, 9 Oct 2020 08:44:39 +1100 (AEDT) Received: by mail-ot1-x330.google.com with SMTP id f37so6994722otf.12 for ; Thu, 08 Oct 2020 14:44:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=K6aXb4BMi9tFQIAIOnmtCcUxdWA9brb3Yj+0K2rLBEA=; b=J3YMMkZVjtSaWPIbnG9MI/NlQRGiBfeK1GpESLpOg3RYvKgO+gr4raMTY/NbEQgDOD j1/uy0prEb9Vz4S+Qe2YMvoOYxb8TW01G3/5h1lHoHNqX7nlQ7NmIsGBKrRTOCsRATWq NfR46M49+x0CMvfkxD2kqBOY02YDeg23T537hUz2582Xho1H+FuTQvWixXe4HOKeW9uK 9GRQ6zC7ey0DqQmFFqgbyxz2qWKGJywWaJRvkJCP9FIsGWEWOrNLnLHB4+CXD/DhUAmq ZH3DF+W1Hniu8gBZubjYyvyJzQXiXGxryeeEs1m9BPhimzDNxHT6nK/r6u0HmEGxpzrh yC9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=K6aXb4BMi9tFQIAIOnmtCcUxdWA9brb3Yj+0K2rLBEA=; b=ckOT3xL5ZXBNUsb5pN5clAdVvQCSNsq/6azhvcnLwy9JykO+tl8t/jYemFLcGnX6A8 77S2iJPvwkJv2I2cpJZkqz+nWKAYXLkoLRhX28+UY5vPCdsmZDHgteTKyYMSB09FZO/K yHzChiRrNpVimjY75Wne5Lcg03H18xuDrz9BwS4P8iygO54dsFbUUa6SghRke5/B0wKB bIJyWlEQbP8oh94pySg7I2OR6qeIU5AWnx/2t8eZi1S2Ouxu58tfTOhrDYMAS2vVhNgS vT37SmK6yW1CqQ5q2UaT8Rh182Dn0sHLgLt54GXoGlXQ0fGyhzyS4r9u5PxVRxh9QoVB tMtw== X-Gm-Message-State: AOAM533/tFu3wlgwkvS+g9iJ/RxVnlXYzh4QeUddYMVHBNdeZkborgk3 pbtnF+VgqCPCJVL2+3IeyAdXdihPRnRTichJ8ufXzZsKjonciA== X-Google-Smtp-Source: ABdhPJwbSB7dukVfV+Dgwn9uqYEvqX0kcdAxKytMtcZpmT+2Nb8wYgwb1rtPoLCMKPUi50DJCjHxspLfHpqGKrejFww= X-Received: by 2002:a9d:3bca:: with SMTP id k68mr6039866otc.150.1602193474596; Thu, 08 Oct 2020 14:44:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Pasha Ghabussi Date: Thu, 8 Oct 2020 17:44:23 -0400 Message-ID: Subject: Re: BMC Performance Profiler To: openbmc@lists.ozlabs.org Content-Type: multipart/alternative; boundary="000000000000ea931905b12fbcb7" 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: , Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" --000000000000ea931905b12fbcb7 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 proposal sent earlier and let us know your thoughts and suggestions. Thank you On Mon, Oct 5, 2020 at 1:57 PM Pasha Ghabussi wrote: > 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 a= t > DBus traffic dumps. Current DBus inspection and visualization tools do no= t > represent the DBus events similar to a typical performance profiler. > Additionally, these tools do not address typical BMC workloads such as IP= MI > 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 t= he > 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=9Chostbo= ot > 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 th= e > 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 webserve= r > 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= such > as type, source, destination, path, interface, demon signatures, and m= ore. > - > > 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 > --000000000000ea931905b12fbcb7 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 proposal sent earlier and let us know your thoughts and suggestio= ns.

Thank you

On Mon, Oct 5, 2020 at = 1:57 PM Pasha Ghabussi <pashag@goog= le.com> wrote:

Hello all,

We would really appreciate it = if you can take a few minutes to read the following proposal and let us kno= w your thoughts and suggestions.

We are developing a tool to investigate perfo= rmance problems by looking at DBus traffic dumps. Current DBus inspection a= nd visualization tools do not represent the DBus events similar to a typica= l performance profiler. Additionally, these tools do not address typical BM= C 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 com= munity, both of which can be helped by this work: IPMI-related issues start= ed to appear as early as in 2017. One issue (#2630) describes a problem related to large numbers of sensors.= Its follow-up (#3098)<= /a> 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 discussion= s on Red= Fish performance on the mailing list; A patch optimized DBus performance by introducing a cac= he for name translation.

All the performance investigations listed above involv= e 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 db= us-pcap, Wireshark, Bustl= e, = Snyh, or DFeet do not provide the exact= functionality we are looking for. Our goal is to develop functionalities s= imilar to other widely used profilers such as GPUView or VTune Profiler.


One alternative solution conside= red was to stream DBus requests over websocket, but the existing websocket = endpoints available on BMC webserver do not provide the exact information w= e need.


Requirements and Scalability:

  • Should provide the adequ= ate functionalities to filter, visualize the events timeline, and group the= DBus traffic based on multiple criteria such as type, source, destination,= path, interface, demon signatures, and more.

  • Should support capture of DBus messages using as little re= sources as possible.

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

  • Integration with webui-vue=


Thank you
--000000000000ea931905b12fbcb7--