All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>,
	bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] regression of 'world' performance?
Date: Fri, 09 Feb 2024 16:22:04 +0000	[thread overview]
Message-ID: <cf9339c32c0923068f0e4ae81fe1ebdb8153b20a.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-3QDJMcqaVTSj+XRZo140O-hg5K9kM8e0mtF7yp=P9Tg@mail.gmail.com>

On Fri, 2024-02-09 at 17:16 +0100, Alexander Kanavin wrote:
> On Fri, 9 Feb 2024 at 17:06, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Iterating 28k entries isn't an issue for python. Yes, it will be "slow"
> > when you put logging around it but I doubt it is the real problem.
> > 
> > What is more likely is one of the calls like:
> > 
> > self.check_dependencies(xxx)
> > 
> > getting called once per entry and that call being slow.
> > 
> > Can you try the profile -P data please. If it doesn't make sense, share
> > it somewhere and I'll take a look.
> 
> I get:
> 
> Parsing of 2966 .bb files complete (0 cached, 2966 parsed). 4758
> targets, 129 skipped, 0 masked, 0 errors.
> ERROR: Command execution failed: Traceback (most recent call last):
>   File "/srv/work/alex/poky/bitbake/lib/bb/cooker.py", line 2284, in parse_next
>     parsed, mc, result = next(self.results)
>                          ^^^^^^^^^^^^^^^^^^
> StopIteration
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/srv/work/alex/poky/bitbake/lib/bb/command.py", line 122, in
> runAsyncCommand
>     self.cooker.updateCache()
>   File "/srv/work/alex/poky/bitbake/lib/bb/cooker.py", line 1635, in updateCache
>     if not self.parser.parse_next():
>            ^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/srv/work/alex/poky/bitbake/lib/bb/cooker.py", line 2293, in parse_next
>     self.shutdown()
>   File "/srv/work/alex/poky/bitbake/lib/bb/cooker.py", line 2244, in shutdown
>     bb.utils.process_profilelog(profiles, pout = pout)
>   File "/srv/work/alex/poky/bitbake/lib/bb/utils.py", line 1159, in
> process_profilelog
>     p = pstats.Stats(*fn, stream=pout)
>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/usr/lib/python3.11/pstats.py", line 116, in __init__
>     self.add(*args)
>   File "/usr/lib/python3.11/pstats.py", line 174, in add
>     item = Stats(item)
>            ^^^^^^^^^^^
>   File "/usr/lib/python3.11/pstats.py", line 115, in __init__
>     self.init(arg)
>   File "/usr/lib/python3.11/pstats.py", line 129, in init
>     self.load_stats(arg)
>   File "/usr/lib/python3.11/pstats.py", line 143, in load_stats
>     self.stats = marshal.load(f)
>                  ^^^^^^^^^^^^^^^
> EOFError: EOF read where object expected


That is very unexpected. I just tested "bitbake bash -P" myself and it
did work out ok. The stack trace doesn't really make sense to me so no
sure what is going on or why this is failing :(

That does look like it might be the post processing code failing (it
saves the results in binary, then loads and processes the logs to be
human readable as it exits).

Cheers,

Richard


  reply	other threads:[~2024-02-09 16:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 10:57 regression of 'world' performance? Alexander Kanavin
2024-01-12 12:13 ` [bitbake-devel] " Richard Purdie
2024-01-12 12:27   ` Alexander Kanavin
2024-01-12 22:19     ` Khem Raj
2024-02-09 15:23       ` Alexander Kanavin
2024-02-09 15:43         ` Richard Purdie
2024-02-09 15:59           ` Alexander Kanavin
2024-02-09 16:05             ` Richard Purdie
2024-02-09 16:16               ` Alexander Kanavin
2024-02-09 16:22                 ` Richard Purdie [this message]
2024-02-09 17:02                   ` Alexander Kanavin
     [not found]                   ` <17B24084174823DE.15017@lists.openembedded.org>
2024-02-09 20:44                     ` Alexander Kanavin
2024-02-09 21:43                       ` chris.laplante
2024-02-09 22:50                         ` chris.laplante
2024-02-09 23:33                       ` Richard Purdie
     [not found]                       ` <17B255DB2CE33879.588@lists.openembedded.org>
2024-02-09 23:59                         ` Richard Purdie
     [not found]                         ` <17B257441406400D.588@lists.openembedded.org>
2024-02-10 15:16                           ` Richard Purdie
     [not found]                           ` <17B2894C95E031D0.14481@lists.openembedded.org>
2024-02-10 20:42                             ` Richard Purdie
     [not found]                             ` <17B29B2072FF51A8.14481@lists.openembedded.org>
2024-02-10 20:52                               ` Richard Purdie
2024-02-12 12:58                                 ` Alexander Kanavin
2024-02-13  8:57                                   ` Richard Purdie
2024-02-13  9:42                                     ` Alexander Kanavin
2024-02-13 12:41                                       ` Richard Purdie
2024-02-14  6:59                                         ` Alexander Kanavin
2024-02-14  8:05                                           ` Richard Purdie
2024-02-13 10:49                                   ` Ross Burton
2024-02-13 12:31                                     ` Richard Purdie

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=cf9339c32c0923068f0e4ae81fe1ebdb8153b20a.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.