[pypy-issue] [issue1115] build error with some options

Armin Rigo tracker at bugs.pypy.org
Fri Apr 13 12:20:03 CEST 2012


Armin Rigo <armin.rigo at gmail.com> added the comment:

Uh, are you annoyed that we didn't answer you in 9 days?  Sorry, I don't follow
each issue every day...

I'm just saying that even on total memory usage, I fear that you cannot have big
wins by specifying any extra option.  Nowadays, the default options for
PyPy-with-JIT are the same as the options that tend to reduce memory usage. 
There are probably small wins to have but no big win.

Even the --gcremovetypeptr option goes into the "small-to-medium" category; it's
not as good as the other optimization we talk about in
http://morepypy.blogspot.com/2009/10/gc-improvements.html --- and that one is on
by default.

Sorry if your program still ends up much bigger on PyPy than on CPython.  This
is the case e.g. if you program is mainly simple var-sized objects like strings,
lists, dicts, and so on --- as opposed to mainly being instances.  You can get
better wins by playing with the GC environment variables, which give at run-time
trade-offs of speed versus memory. 
https://bitbucket.org/pypy/pypy/raw/default/pypy/rpython/memory/gc/minimark.py

________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue1115>
________________________________________


More information about the pypy-issue mailing list