From: "Livius" <egyszeregy@freemail.hu>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2 0/4] bitbake: knotty/progressbar: Optimize footer update and prints.
Date: Sat, 25 Jan 2025 03:35:01 -0800 [thread overview]
Message-ID: <6995.1737804901994832161@lists.openembedded.org> (raw)
In-Reply-To: <4c4373f1f496cf2cf3cba8f1716fef7b21871d4f.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Performance improvement is quite trivial that will happen. Not allowed to write to stdout or any unbuffered file while the code is running inside a loop in any script language or programming language.
I started to look for the performance issues because my Yocto projects started to build slowly from scarthgap release in any physical machines (only in a virtual machine it can run fast yet).
https://lists.openembedded.org/g/bitbake-devel/topic/109854844
Yesterday, I found the bug which releated to bitbake Event logger (workaround to disable it). Soon I will send a Patch v3 for footer update, but not this was the root cause, i will also send a patch for fix even logger class logging which has the real critical problem.
[-- Attachment #2: Type: text/html, Size: 848 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Livius" <egyszeregy@freemail.hu>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2 0/4] bitbake: knotty/progressbar: Optimize footer update and prints.
Date: Sat, 25 Jan 2025 03:35:40 -0800 [thread overview]
Message-ID: <6995.1737804901994832161@lists.openembedded.org> (raw)
Message-ID: <20250125113540.AuTVNjLnDmVNjnSNVYuD0cA5_JKaJWtxS1SAPYSb6ho@z> (raw)
In-Reply-To: <4c4373f1f496cf2cf3cba8f1716fef7b21871d4f.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
Performance improvement is quite trivial that will happen. Not allowed to write to stdout or any unbuffered file while the code is running inside a loop in any script language or programming language.
I started to look for the performance issues because my Yocto projects started to build slowly from scarthgap release in any physical machines (only in a virtual machine it can run fast yet).
https://lists.openembedded.org/g/bitbake-devel/topic/109854844
Yesterday, I found the bug which releated to bitbake Event logger (workaround to disable it). Soon I will send a Patch v3 for footer update, but not this was the root cause, i will also send a patch for fix even logger class logging which has the real critical problem.
[-- Attachment #2: Type: text/html, Size: 857 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Livius" <egyszeregy@freemail.hu>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2 0/4] bitbake: knotty/progressbar: Optimize footer update and prints.
Date: Sat, 25 Jan 2025 03:36:36 -0800 [thread overview]
Message-ID: <6995.1737804901994832161@lists.openembedded.org> (raw)
Message-ID: <20250125113636.Hpo4s-l5METx0PR8eNOXJwG8L1XFfjyI54ItF27RUCc@z> (raw)
In-Reply-To: <4c4373f1f496cf2cf3cba8f1716fef7b21871d4f.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
Performance improvement is quite trivial that will happen. Not allowed to write to stdout or any unbuffered file while the code is running inside a loop in any script language or programming language.
I started to look for the performance issues because my Yocto projects started to build slowly from scarthgap release in any physical machines (only in a virtual machine it can run fast yet).
https://lists.openembedded.org/g/bitbake-devel/topic/109854844
Yesterday, I found the bug which releated to bitbake Event logger (workaround to disable it). Soon I will send a Patch v3 for footer update, but not this was the root cause. I will also send a patch for fix even logger class logging which has the real critical problem.
[-- Attachment #2: Type: text/html, Size: 857 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Livius" <egyszeregy@freemail.hu>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2 0/4] bitbake: knotty/progressbar: Optimize footer update and prints.
Date: Sat, 25 Jan 2025 03:37:07 -0800 [thread overview]
Message-ID: <6995.1737804901994832161@lists.openembedded.org> (raw)
Message-ID: <20250125113707.lTDFGX-9C2rsdIMC4wS6aYzBIn1heLUFMXqD5q2GJ2A@z> (raw)
In-Reply-To: <4c4373f1f496cf2cf3cba8f1716fef7b21871d4f.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Performance improvement is quite trivial that will happen. Not allowed to write to stdout or any unbuffered file while the code is running inside a loop in any script language or programming language.
I started to look for the performance issues because my Yocto projects started to build slowly from scarthgap release in any physical machines (only in a virtual machine it can run fast yet).
https://lists.openembedded.org/g/bitbake-devel/topic/109854844
Yesterday, I found the bug which releated to bitbake Event logger (workaround to disable it). Soon I will send a Patch v3 for footer update, but not this was the root cause. I will also send a patch for fix event logger class logging which has the real critical problem.
[-- Attachment #2: Type: text/html, Size: 858 bytes --]
next prev parent reply other threads:[~2025-01-25 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 23:24 [PATCH v2 0/4] bitbake: knotty/progressbar: Optimize footer update and prints egyszeregy
2025-01-22 23:24 ` [PATCH v2 1/4] bitbake: progressbar: Check resizable file descriptor egyszeregy
2025-01-22 23:58 ` [bitbake-devel] " Richard Purdie
2025-01-22 23:24 ` [PATCH v2 2/4] bitbake: knotty: Use a StringIO buffer for update footer egyszeregy
2025-01-22 23:24 ` [PATCH v2 3/4] bitbake: knotty: Use 10 Hz refresh rate (FPS) for footer update egyszeregy
2025-01-22 23:24 ` [PATCH v2 4/4] bitbake: knotty: print() was eliminated from all loops for better performance egyszeregy
2025-01-23 0:01 ` [bitbake-devel] [PATCH v2 0/4] bitbake: knotty/progressbar: Optimize footer update and prints Richard Purdie
2025-01-25 11:35 ` Livius [this message]
2025-01-25 11:37 ` Livius
2025-01-25 11:36 ` Livius
2025-01-25 11:35 ` Livius
2025-04-18 13:56 ` Livius
2025-04-18 13:57 ` Livius
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=6995.1737804901994832161@lists.openembedded.org \
--to=egyszeregy@freemail.hu \
--cc=bitbake-devel@lists.openembedded.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 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.