I have no idea how memory management works on windows (I doubt this will solve it), but this is how we do that on linux
On Mon, Mar 7, 2016 at 10:55 AM, Yury V. Zaytsev <y...@shurup.com> wrote: > On Sun, 6 Mar 2016, Maciej Fijalkowski wrote: > >> It uses subprocess, but you need to quit pypy (so run this with --source >> and then make separately) for memory to be reclaimed > > > Do you think that pre-forking a process for compilation right at the > beginning of the translation when PyPy hasn't consumed much memory yet would > be a viable solution? > > I think if this is practical, it would be a much user friendlier solution as > compared to two-step process (translation + compilation). If memory serves > me well, this is one of the strategies that subprocess in Python 3 is using > to improve on memory consumption. > > > -- > Sincerely yours, > Yury V. Zaytsev _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
