From: lubrito@posteo.net
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Outreachy: Timeline tasks
Date: Thu, 29 Apr 2021 16:02:54 +0000 [thread overview]
Message-ID: <mid:1> (raw)
In-Reply-To: 87v986dvrn.fsf@cbaines.net
Hi,
On Wed, 28 Apr 2021 21:00:44 +0100
Christopher Baines <mail@cbaines.net> wrote:
> I think time is the main thing, since that alone will help to identify
> which are the slow parts.
> Indeed, simplicity is a good thing to keep in mind.
I'll keep in mind what you have said, so here are some ideas to
break the tasks.
Task 1: Add instrumentation to identify the slow parts of processing
new revisions
- Implementing a chart over time to identify slow parts;
- Select candidate parts to be analyzed;
- Should this part really be taking all this time?
- Identify if the delay is caused by the code itself or by a
query.
- Prepare a document organizing where each part should
be improved.
Task 2: Improve the performance of these slow parts
- implementing each improvements.
This Task 2 is really difficult for me to divide in smaller tasks, I'm
really stuck with ideas.
I took a look at one of the logs as you told me, and I found this parts
taking a considerable time:
- Computing the channel derivations 636s
- Acquiring advisory transaction lock:
loading-new-guix-revision-inserts 2534s *
- Getting derivation lint warnings 975s
- fetching inferior lint warnings 1488s
- Acquiring advisory transaction lock:
loading-new-guix-revision-inserts 3226s *
- Querying the temp-package-metadata 1949s
- Fetching inferior package metadata 2476s
To pick this parts is what should be facilitated by the chart?
So I would perform the analysis of the task 1 and then the ta
By the way, I noticed that the ones I marked with * are performed twice.
Why is that?
--
Best Regards,
Luciana Lima Brito
MSc. in Computer Science
next prev parent reply other threads:[~2021-04-29 16:07 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 [this message]
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
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='mid:1' \
--to=lubrito@posteo.net \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.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).