Hi RP,
On 11/9/21 6:26 PM, Richard Purdie wrote:
On Tue, 2021-11-09 at 10:56 +0100, Alexander Kanavin wrote:
On Tue, 9 Nov 2021 at 10:51, Robert Yang wrote:
Maybe, but once we start doing tweaks like this, where do they stop? Hey,
I'd
I think that it's not only a performance tweak, but
On Tue, 2021-11-09 at 10:56 +0100, Alexander Kanavin wrote:
> On Tue, 9 Nov 2021 at 10:51, Robert Yang wrote:
> > > Maybe, but once we start doing tweaks like this, where do they stop? Hey,
> > I'd
> >
> > I think that it's not only a performance tweak, but this should be
> > considered
> > as
On Tue, 9 Nov 2021 at 10:51, Robert Yang wrote:
> > Maybe, but once we start doing tweaks like this, where do they stop?
> Hey, I'd
>
> I think that it's not only a performance tweak, but this should be
> considered as
> a bug since it would be failed to build on powerful machine, which isn't
>
Hi Alexander,
On 11/9/21 5:44 PM, Alexander Kanavin wrote:
Maybe, but once we start doing tweaks like this, where do they stop? Hey, I'd
I think that it's not only a performance tweak, but this should be considered as
a bug since it would be failed to build on powerful machine, which isn't
Hi Alexander,
On 11/9/21 4:21 PM, Alexander Kanavin wrote:
But does this mean we need to globally restrict this and make things twice
slower for everyone? I'm not sure.
Please see my reply to Konrad, it doesn't cause any slower, but faster in my
testing.
BTW, the XZ_MEMLIMIT is 50% for
Maybe, but once we start doing tweaks like this, where do they stop? Hey,
I'd like to limit llvm and webkit threads too, they eat disproportionally
large amounts of RAM compared to everything else! I'd rather err on the
side of simple, striaghtforward, universal defaults, and having better
On 11/9/21 4:41 PM, Konrad Weihmann wrote:
On 09.11.21 09:48, Robert Yang wrote:
The original value is very easy to cause do_packge error when cpu number is
larger, for example, 128 cores and 512G mem:
error: create archive failed: cpio: write failed - Cannot allocate memory"
Set the
Robert Yang escreveu no dia terça, 9/11/2021
à(s) 08:12:
> The original value is very easy to cause do_packge error when cpu number is
> larger, for example, 128 cores and 512G mem:
>
> error: create archive failed: cpio: write failed - Cannot allocate memory"
>
> Set the ZSTD_THREADS to half of
On 09.11.21 09:48, Robert Yang wrote:
The original value is very easy to cause do_packge error when cpu number is
larger, for example, 128 cores and 512G mem:
error: create archive failed: cpio: write failed - Cannot allocate memory"
Set the ZSTD_THREADS to half of the CPU number can avoid
But does this mean we need to globally restrict this and make things twice
slower for everyone? I'm not sure.
Alex
On Tue, 9 Nov 2021 at 09:12, Robert Yang wrote:
> The original value is very easy to cause do_packge error when cpu number is
> larger, for example, 128 cores and 512G mem:
>
>
The original value is very easy to cause do_packge error when cpu number is
larger, for example, 128 cores and 512G mem:
error: create archive failed: cpio: write failed - Cannot allocate memory"
Set the ZSTD_THREADS to half of the CPU number can avoid the error in my
testing.
Signed-off-by:
11 matches
Mail list logo
