From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id HNarNrLhjWChUgEAgWs5BA (envelope-from ) for ; Sun, 02 May 2021 01:18:10 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id 4PPCMbLhjWCGCAAAB5/wlQ (envelope-from ) for ; Sat, 01 May 2021 23:18:10 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 8CA2E1B6FD for ; Sun, 2 May 2021 01:18:10 +0200 (CEST) Received: from localhost ([::1]:50618 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lcysD-00036U-OG for larch@yhetil.org; Sat, 01 May 2021 19:18:09 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:54248) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lcys4-00036N-9F for guix-devel@gnu.org; Sat, 01 May 2021 19:18:00 -0400 Received: from mout02.posteo.de ([185.67.36.66]:34707) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lcys1-0006xy-Ch for guix-devel@gnu.org; Sat, 01 May 2021 19:17:59 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 8A4DA2400FC for ; Sun, 2 May 2021 01:17:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1619911073; bh=SzPztjZaldEP4hKCDz0XlloSIijGbxmjggKsyGEKIr8=; h=Date:From:To:Cc:Subject:From; b=qhRivnPdQ3/dTDVqj6k3lM93+ehPWC5uRowRAH8icRWzBdqHIodrHx12nAnX7aTBQ jZRXijrMDgjhnsIFecVmyhqA5riYvSr0CiSmQH9Ig5FGTI5FD7B5yMC6cNQ/deUeRN zCVVN1RSNC3QsVVLpD4Sf9QgGSb1p4JC79VndIrQH8s98KIPfUTOwMSif5wCA3IcEz 6pfWPH+D5w7B0R0G0lStoMgtIavxj4iAunrUjBPOlKTuuTfng5m1va5oe0Y3n7EY/B WUO1+MEpfmbL3WRTQHjZ2QudWvpl+JmQCS5J+fn/h5xaABTf/+eKB1Noaxm2E+Ifwy Mef58M/pt/V3w== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4FXlWz4KCMz6tm9; Sun, 2 May 2021 01:17:51 +0200 (CEST) Date: Sat, 1 May 2021 23:17:43 +0000 From: Luciana Lima Brito To: Christopher Baines Subject: Re: Outreachy: Timeline tasks Message-ID: <20210501201743.53a10b7f@lubrito> In-Reply-To: <875z02e0hf.fsf@cbaines.net> References: <20210428145941.4bd0dd6f@lubrito> <87y2d2e0j4.fsf@cbaines.net> <20210428162030.2cab4106@lubrito> <87v986dvrn.fsf@cbaines.net> <87bl9ueunr.fsf@cbaines.net> <20210501104811.44bd2e4d@lubrito> <875z02e0hf.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=185.67.36.66; envelope-from=lubrito@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1619911090; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=9Z9Fgck84DMP1t1i64dT4pQc9/ixwmhCiNRECRfgBaM=; b=fgES5m/AXD+wy1DzI/ySlDNtScZxdDMS6Z22K8GJPVAYmaqxHBDrIQlBbaXy6OQYHM+6hO Y6y/lv/Zqm8rT1ixTOJYBhj163JUXnEm4cPpm8HewWYDUBNVtZWImuXU6FvVaP9HqXh1uJ 1xnC8CIaYHwd6TnZGPTQ1HESzqTOwj/CeYYzGtXeKLj6lzVQkGZSrmYVRwuYEc+LVPNm+E snhsVT1nVhlcHEB2qb8eaA0Z/7JZoR5yLiJ/GNbl171nj0kpS66a2ZPGeINE3950tmxvpB YGdFQiBRpldUv0om5N4M8mQQMvVC1W49faUo0CTg5rFgOZAHDrrIzja+cg//cA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1619911090; a=rsa-sha256; cv=none; b=um7MJgBa7rhLDGq4pwtxnplQq9kTyQnzKul8/AbDi2FhJEjgiBC4SzuJ5+vU6KOynQQF/B 0lfTULdNvYL5ZS2IWqaVbUD0SNP/T9FodEJIZXRT2nywvcXvmHQDKTqWvyd0vz1VC8uXaw W2anCMs92dHafPIUF2LMI50qQDef+ymjGpOPwTzID7ltvbRWD48+18dmiNOaYCU7zLbKM/ VUNvdXrUKEg9gERDGtdrdIS7yNq7Ny3/3niY+Yi/68gIjZhDZrz89rsHHv8dOW8RkhVy5L WI3QxVH7hTVgolPIDWFoOXDO4TYOvR6vyZUPdlK85I66oSllraDnRxzsMdZ0qA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=qhRivnPd; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Spam-Score: -2.66 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=qhRivnPd; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: 8CA2E1B6FD X-Spam-Score: -2.66 X-Migadu-Scanner: scn0.migadu.com X-TUID: xFiOEIUuqgFp On Sat, 01 May 2021 20:07:56 +0100 Christopher Baines wrote: > Luciana Lima Brito writes: > > > On Sat, 01 May 2021 09:16:08 +0100 > > Christopher Baines wrote: > > > >> Currently the timing of various sections of the process includes > >> timing smaller sections, and that may complicate reading the chart, > >> since it won't convey which timed sections include other timed > >> sections. Does that make sense? > > > > Yes, I understand. But just to make sure, you say that the actions > > we see in the logs are actually subsections of a bigger process? The > > problem here would be to clearly mark in the code actions of a same > > process. I'll take this into account on my planning. > > Take the lint warnings for example, currently the time to fetch all > lint warnings is timed, but the usage of each individual linter is > timed. Both bits of information are helpful. OK. > > For that I propose to build 2 charts, one of the > > macro view, what we call "overview first", showing the > > sections(processes) and their whole time taken. This way we could > > just see what we were aiming for, which is to identify slowness. > > The second chart would be what we call "details on demand", in > > which we could have the subsections(actions) being shown. To differ > > to which section(process) they are bound, we could use two > > meaningless alternating colours (just to group the subsections of a > > section), and they would follow the same order as the first chart. > > > > The use of alternating colours could be applied to both charts in > > order to make clear the equivalence. Both charts should appear at > > the same time, one above the other, to ease comparison. > > That sounds better, although I think a timeline, similar to what the > systemd-analyze example uses [1] might be a more natural > representation of the data, colour could then be used to represent > relatively how long each part takes. > > 1: https://lizards.opensuse.org/wp-content/uploads/2012/07/plot001.gif Here I have two observations to debate: 1 - Is the starting and ending time of each process an important information to determine its slowness? If this information is not necessary, maybe we should avoid the timeline, in order to make the chart cleaner. A timeline could impair the comparisons of bars, so I would recommend simple bar charts. 2 - About the colours to represent how long each part takes, I don't know if I get it right. Do you mean to have one colour for slow parts and other colour to normal parts? Anyway, I think all this can be further discussed while the work is in progress. > > I'll add this to the plan and to the final application, ok? > > Yep. -- Best Regards, Luciana Lima Brito MSc. in Computer Science