public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Performance tuning and parallelisation
Date: Tue, 31 Aug 2021 09:00:14 +0100	[thread overview]
Message-ID: <a6c07377-3748-da61-cd82-7e27193934d1@wildgooses.com> (raw)
In-Reply-To: <20210826163815.vr7jtxkwuqz37wyz@Ridl3y>

[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]

On 26/08/2021 17:38, Marco Sirabella wrote:
> -
>
> Hi Ed,
>
> I’ve taken a dabble at trying to track down portage’s bottlenecks (and have stopped for the time
> being at solving them :/ )
>
>     Can anyone give me a leg up on how I could benchmark this further and look for the hotspot?
>     Perhaps someone understand the architecture of this point more intimately and could point at
>     whether there are opportunities to do some of the processing on mass, rather than per file?
>
> From my notes at the timem, it looks like yappi <https://pypi.org/project/yappi/> worked a bit
> better than python’s built in cProfile for me because it properly dove into async calls. I used
> snakeviz <https://jiffyclub.github.io/snakeviz/> for visualizing the profile results.
>
> I was taking a look at depclean, but I found similarly that a lot of duplicate process was being
> done due to encapsulated abstractions not being able to communicate that the same thing was being
> done multiple times eg removing each package processes a massive json structure for each package
> removed, although I opted to work on the more-understandable unicode conversions.
>
> My stalled progress can be found here: #700 <https://github.com/gentoo/portage/pull/700>. Lost the
> drive to continue for now unfortunately :<
>
> Good luck! Looking forward to your optimizations
>
> – Marco Sirabella
>

Hi All, thanks for the replies. Wow, Marco, that patch touches a lot of stuff...!

OK, I will start by trying to get the profilers going and work from there...

(Alec, to avoid replying separately: Thanks for your notes. Yes, I am not clear which of the
install/merge phases specifically is the culprit, but it feels like something in that area is
"slow", especially when run under qemu user mode. I think using qmerge won't work for my build
script, but great idea to use it for benchmarking to narrow things down - thanks)

Thanks all

Ed W


[-- Attachment #2: Type: text/html, Size: 3490 bytes --]

  reply	other threads:[~2021-08-31  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 11:03 [gentoo-portage-dev] Performance tuning and parallelisation Ed W
2021-08-26 16:38 ` Marco Sirabella
2021-08-31  8:00   ` Ed W [this message]
2021-08-27 20:50 ` Alec Warner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a6c07377-3748-da61-cd82-7e27193934d1@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox