FWIW: I'm mounting my OE drives with barrier=0 and ext4 without journal
(commit=1 cannot be used on ext4 without journal)
BTW: During last OE Happy Hours Khem mentioned using F2FS on NVMEs, anyone
else already played with it?
Not sure how different the effect is from the suggested sysctl
Hi,
One related improvement is to avoid IO to disk completely as long as RAM is
available. By default file systems like ext4 will start writing all buffers
in the background after few seconds which is wasted IO if memory is available
and
rm_work will anyway wipe the tmp to produce a target
> My oldest NVME dedicated for OE builds, bought 2019-11-24
> https://www.gigabyte.com/SSD/AORUS-NVMe-Gen4-SSD-2TB#kf
> with 3600TBW, shows 60% Estimated Remaining Life after around 21K running
hours and started disconnecting under heavy load (not necessary issue
caused by wear) about a year ago
On Fri, Sep 8, 2023 at 9:20 AM Alexandre Belloni <
alexandre.bell...@bootlin.com> wrote:
> On 08/09/2023 09:06:39+0200, Martin Jansa wrote:
> > On Fri, Sep 8, 2023 at 8:42 AM Yoann Congal
> wrote:
> >
> > > Hi!
> > > Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN <
> hassanchatta...@gmail.com>
>
Hello Mohammed,
On Fri, 8 Sep 2023 at 09:18, MOHAMMED HASSAN
wrote:
> My builds on an average take 15-20 mins with the build folder intact.
> How much time do you think it will take on average with rm_work enabled?
>
Depends on what changed. If nothing changed, time remains the same, except
On 08/09/2023 09:06:39+0200, Martin Jansa wrote:
> On Fri, Sep 8, 2023 at 8:42 AM Yoann Congal wrote:
>
> > Hi!
> > Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN
> > a écrit :
> >
> >> Right, you're not the only one!
> >> See
> >>
> >>
My builds on an average take 15-20 mins with the build folder intact.
How much time do you think it will take on average with rm_work enabled?
Regards,
Hassan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60946):
On Fri, Sep 8, 2023 at 8:42 AM Yoann Congal wrote:
> Hi!
> Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN
> a écrit :
>
>> Right, you're not the only one!
>> See
>>
>> https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space
>> and
Hi!
Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN a
écrit :
> Right, you're not the only one!
> See
>
> https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space
> and https://docs.yoctoproject.org/dev/dev-manual/disk-space.html
>
> I can use rm_work and remove
>
>
> Right, you're not the only one!
> See
> https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space
>
> and https://docs.yoctoproject.org/dev/dev-manual/disk-space.html
I can use rm_work and remove all the build related files, however every
subsequent build
Hi Hassan
On 08.09.23 at 07:02, MOHAMMED HASSAN wrote:
Hi guys,
I wanted to build images for different architectures and machine types
on one SDK. I know that the build directory takes a lot of space (in
my case more than 90 GB). What to do in such a case.
Are they any efficient techniques
Hi guys,
I wanted to build images for different architectures and machine types on
one SDK. I know that the build directory takes a lot of space (in my case
more than 90 GB). What to do in such a case.
Are they any efficient techniques that you can share with me?
Thanks and regards,
Hassan
12 matches
Mail list logo
