[pypy-dev] Parallel translation?

Maciej Fijalkowski fijall at gmail.com
Sat Dec 5 17:49:37 CET 2009

On Sat, Dec 5, 2009 at 4:44 PM, Armin Rigo <arigo at tunes.org> wrote:
> Hi,
> On Fri, Dec 04, 2009 at 06:18:13PM +0100, Antonio Cuni wrote:
>> I agree that at this point in time we cannot or don't want to make
>> annotation/rtyping/backend parallelizable, but it should definitely be
>> possible to just pass the -j flag to 'make' in an automatic way.
> Of course, that is full of open problems too.  The main one is that each
> gcc process consumes potentially a lot of RAM, so just passing "-j" is
> not a great idea, as all gccs are started in parallel.  It looks like
> some obscure tweak is needed, like setting -j to a number that depends
> not only on the number of CPUs (as is classically done) but also on the
> total RAM of the system...
> A bientot,
> Armin.

I guess the original idea was to have a translation option that is
passed as -j flag to make, so one can specify what number of jobs he
wants, instead of trying to guess it automatically.


More information about the Pypy-dev mailing list