From: Christopher Baines <mail@cbaines.net>
To: Luciana Lima Brito <lubrito@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: Outreachy: Timeline tasks
Date: Sun, 02 May 2021 10:20:56 +0100 [thread overview]
Message-ID: <87zgxdcwzr.fsf@cbaines.net> (raw)
In-Reply-To: <20210501201743.53a10b7f@lubrito>
[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]
Luciana Lima Brito <lubrito@posteo.net> writes:
> On Sat, 01 May 2021 20:07:56 +0100
> Christopher Baines <mail@cbaines.net> wrote:
>
>> Luciana Lima Brito <lubrito@posteo.net> writes:
>>
>> > 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.
I think what things are happening when is relevant, but that's more
about understanding the hierarchy, rather than specific start and end
times.
> 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?
Basically, although using more colours (from a gradient, like white to
red) would probably convey more information than just two colours.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2021-05-02 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 17:59 Outreachy: Timeline tasks Luciana Lima Brito
2021-04-28 18:17 ` Christopher Baines
2021-04-28 19:20 ` Luciana Lima Brito
2021-04-28 20:00 ` Christopher Baines
2021-04-29 16:02 ` lubrito
2021-04-29 20:14 ` Christopher Baines
2021-04-30 15:44 ` Luciana Lima Brito
2021-04-30 17:05 ` Christopher Baines
2021-04-30 21:19 ` Luciana Lima Brito
2021-05-01 8:16 ` Christopher Baines
2021-05-01 13:48 ` Luciana Lima Brito
2021-05-01 19:07 ` Christopher Baines
2021-05-01 23:17 ` Luciana Lima Brito
2021-05-02 9:20 ` Christopher Baines [this message]
2021-05-03 14:23 ` Luciana Lima Brito
2021-05-03 15:29 ` Christopher Baines
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgxdcwzr.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=lubrito@posteo.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).