On Sun, Jun 25, 2006 at 09:07:40PM +0200, Wouter Verhelst wrote:
> It's not a question of legislating; it's more a question of picking a
> good option and writing the specification in policy.
I fully agree with Wouter on this. Although the specification doesn't
necessarily have to be in policy (
On Sun, Jun 25, 2006 at 06:11:24PM +0300, Lars Wirzenius wrote:
> su, 2006-06-25 kello 16:36 +0200, Wouter Verhelst kirjoitti:
> > It has come to my attention that the gem package is currently built
> > using 'make -j 4', to have four compiler processes running at the same
> > time. This is a bit t
On Sun, Jun 25, 2006, Lars Wirzenius wrote:
> Sure, even on a single CPU -jX (X > 1) can be faster, but it depends on
> various factors, such as available memory, and other load on the
> machine. Using -j is not something that should be on by default, but it
> would be *really* nice if it were eas
Lars Wirzenius <[EMAIL PROTECTED]> wrote:
> > It has come to my attention that the gem package is currently built
> > using 'make -j 4', to have four compiler processes running at the same
> > time. This is a bit troublesome for the poor m68k buildd, which is now
> > suffering under High Load And C
su, 2006-06-25 kello 10:41 -0700, Tyler MacDonald kirjoitti:
> kernel-package uses the CONCURRENCY_LEVEL envrionment variable for
> this. And if I do a "CONCURRENCY_LEVEL=4" on my single-CPU system, it does
> actually go quite a bit faster. :)
Sure, even on a single CPU -jX (X > 1) can be fa
On Sun, 2006-06-25 at 16:56 +0200, Bastian Blank wrote:
> DoS against the buildd?
> There is none. But you may consider it as an attack against the
> infrastructure.
You on the other hand, might consider that developers might not have the
malicious intent you infer, but perhaps just made an hones
su, 2006-06-25 kello 16:36 +0200, Wouter Verhelst kirjoitti:
> It has come to my attention that the gem package is currently built
> using 'make -j 4', to have four compiler processes running at the same
> time. This is a bit troublesome for the poor m68k buildd, which is now
> suffering under High
On Sun, Jun 25, 2006 at 04:36:08PM +0200, Wouter Verhelst wrote:
> It has come to my attention that the gem package is currently built
> using 'make -j 4', to have four compiler processes running at the same
> time. This is a bit troublesome for the poor m68k buildd, which is now
> suffering under
Hi,
It has come to my attention that the gem package is currently built
using 'make -j 4', to have four compiler processes running at the same
time. This is a bit troublesome for the poor m68k buildd, which is now
suffering under High Load And Constant Swapping (HLACS).
I was going to file a flam
9 matches
Mail list logo
