[pypy-dev] why PyPy build takes so much resources?

Amaury Forgeot d'Arc amauryfa at gmail.com
Tue Jan 24 18:47:00 CET 2012

2012/1/24 Dmitrey <dmitrey15 at ukr.net>

> Required 4 GB for 64bit machine and lots of time for build to be elapsed
> each day is very inconvenient. Well, I can download and install compiled
> version, but then I have to set all paths to the files I'm working with.
> Maybe somewhere there are lots of C files with -O3 or like that? Can you
> provide a build option e.g. --without-optimization to remove those -O3, -O2
> or somehow else reduce build time and memory consumption (well I see the
> opts
> PYPY_GC_MAX_DELTA=200MB pypy --jit loop_longevity=300 ./translate.py -Ojit
> from http://pypy.org/download.html#**building-from-source<http://pypy.org/download.html#building-from-source>
> but they essentially increase build time).

Yes, pypy takes a long time and a lot of memory to translate.
But this is not because of C files: if you look at the output,
you'll see that the generation and compilation of C source files
is a small part of the whole process -- and memory usage is
already at its highest then.

To reduce translation time and memory, you can use -O2 instead of -Ojit
-- but of course there won't be any JIT.
That's the option I often use, because I'm primarily interested
in the correctness of the resulting interpreter, not its speed.

Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20120124/45f7b44b/attachment.html>

More information about the pypy-dev mailing list