From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 2GkPBPV8jGCxGwEAgWs5BA (envelope-from ) for ; Fri, 30 Apr 2021 23:56:05 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id sGhgO/R8jGBWcwAAB5/wlQ (envelope-from ) for ; Fri, 30 Apr 2021 21:56:04 +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 8799A2729E for ; Fri, 30 Apr 2021 23:56:04 +0200 (CEST) Received: from localhost ([::1]:53612 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lcb7D-0005cH-MX for larch@yhetil.org; Fri, 30 Apr 2021 17:56:03 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:33802) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lcaXe-0005eS-8z for guix-devel@gnu.org; Fri, 30 Apr 2021 17:19:18 -0400 Received: from mout02.posteo.de ([185.67.36.66]:39421) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lcaXb-0000rO-DA for guix-devel@gnu.org; Fri, 30 Apr 2021 17:19:17 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 9F0A12400FC for ; Fri, 30 Apr 2021 23:19:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1619817552; bh=gDu0gz9SLCzl+JjcQNYmQHRW82C2yW4ZZrx0z988Dz4=; h=Date:From:To:Cc:Subject:From; b=RexLcgVaU/Qd3EWk196/n1D5had5wtZxgP7SIb63eduM9rPE2iFgvBzZ8U+x7Flf5 tBukhNIo1hgvO56HXu4U4K6olpxs3zzjA4Mz7QLVPYRRZxMuCFPp9joN5InZj0D4QB TdqEI0UWcrZ/oaDUilK1d4SER2aBL90mvKyRnyuKxWOyEHBKTHT5+3Nb2Nrru4Gmi+ x8XGPTl8hfA1JIsAcml8ERUrO1YCW/yBfsmu6S3FeF4JDuNR8UuwlBTPmU+N6S50eq nnVCOFOb+gvfrQYXuus/dUFt/2hOLW3E8EhBPm1SwMNUOIwx0Apl5P5nZ0jo067ENp SUO10du/O05gg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4FX4xV4bSQz6tmL; Fri, 30 Apr 2021 23:19:10 +0200 (CEST) Date: Fri, 30 Apr 2021 21:19:02 +0000 From: Luciana Lima Brito To: Christopher Baines Subject: Re: Outreachy: Timeline tasks Message-ID: <20210430181902.3e7baaf3@lubrito> In-Reply-To: <87eeerem9g.fsf@cbaines.net> References: <20210428145941.4bd0dd6f@lubrito> <87y2d2e0j4.fsf@cbaines.net> <20210428162030.2cab4106@lubrito> <87v986dvrn.fsf@cbaines.net> <87mttgetm5.fsf@cbaines.net> <20210430124443.561fb340@lubrito> <87eeerem9g.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=1619819764; 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=BsNY6YS0sUUISyV3JviktqSI+FR1IEfdfTcchHoCJSE=; b=pFlBWh8TMQSTirGYoxwYJKi3VOBC0//x+UCv5ZIXAfiyTy9dgd5KUvG88/KvudFxGqCuv8 3GQ5FOk73Bu42yzcR/TvIDXDU8iXDrVFRYsWjl3rgiGbw2qqj4dyTv201odd7oxhhR1eQj erW+eIgJ4yS1GG9ZON7/aJwRf2G3tYE/pylZsHrHG+9+3J6hO9P0S0KoKoLb16g9phYmTn xPqpa/jwPVF6nrN/Q15F5ySfOv+sm9sarriiXFITGD7LKwVV/26T8DI74aZBzeKdxgBsog fQeHVliYtoSCht9FelRZVc6wOfNydfmRmQjohYBpBJccPUEIkkiLs0oltN4fIA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1619819764; a=rsa-sha256; cv=none; b=Mm4grrBJu4sVPnXcqxfAmGduAX3pBnk0MrLisXnVcfF5kwU/U3Bcs3CIm+Kj0vLDRtgL1c FRIoSv36ZAHbBdtM+iUEfuSMyR6Q4oWO88XaT2n8Z5qt8lyiwe4+FX+b78tM1Ve8C9EIPp dT2TLeTDysab98vCEhHcxyY4NJKnMBnE/pO8AOlLsHZZebrc7OtjQltACYz7Onut+/jFP8 Nqy1Dt+72/JOOVjsGydrBuTh8ScPyy0xXL5sO/caLelp+0/LlKeBjF6RMIC2bzfTlskHR7 1TMl7B3ojGMv4F/yQ/lErhde/y2Lcwq08NQ9+oE9lQNbMdS/WMI3/MZEySgKNg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=RexLcgVa; 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=RexLcgVa; 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: 8799A2729E X-Spam-Score: -2.66 X-Migadu-Scanner: scn0.migadu.com X-TUID: rWSqzB/BP6g/ On Fri, 30 Apr 2021 18:05:15 +0100 Christopher Baines wrote: > > > > Task 1: Add instrumentation to identify the slow parts of processing > > new revisions: > > > > - Implementing a chart over time to identify slow parts: > > - The chart should consider two aspects, the time took by > > each specific part, and its name, for identification > > purpose. A bar chart is a good candidate for this task, it is > > simple and can show the whole picture of the time taken by the > > system to process a new revision; > > - The bars on the chart should be sorted in order of > > precedence of the process in the X axis, and its height, which > > is determined by the time it takes, measured in the Y > > axis; > > I'm not sure what you mean by "precedence of the process" here? As we are concerned only with the time each process takes, and each bar on the chart will be presented side by side, the order of the bars would be the order that the processes appear. If you prefer, they could be sorted alphabetically, or by time taken. > > - The charts should work as picture-logs for timing; > > - A chart should be generated for each new revision in real > > time; > > It would be good to say explicitly how the chart will be stored, since > "the same way as the logs already are" is quite vague. I misunderstood this point so this part about storing the chart is completely messed. But I think now I got it. Let me correct the last point and add some more: ... - The time is already being computed for each part and it is shown in the logs, the same data can be used to build the charts. The data to build the chart for each revision could be stored as a new table in the database*, first in parts, for when a revision is still being processed, then combining their parts when the processing is finished. - The new table on the database should store three information: the job_id, the action, and the time taken. - Then, when one wants to see the chart, this table is queried and the chart is rendered as html. * Although the information is already in the log, it is stored as a text, so it is harder to get the names of the actions and the time taken by each, so I think that create a new table, with only these values, is more suitable. > > Great, this is more like it. :) -- Best Regards, Luciana Lima Brito MSc. in Computer Science