Hi Robert. Generally keeping pypy as a daemon and then running small workloads sounds like a good idea. The forking part I don't like because while it might mitigate some warmup, it's much harder to get right. You don't quite know how to push enough calls to JIT the correct paths etc.. However, if you don't fork you're responsible for cleaning up your own state (so e.g. any imports).
Cheers, fijal On Thu, Jul 16, 2015 at 6:21 PM, Robert Grosse <n210241048...@gmail.com> wrote: > One of the main problems with a JIT as opposed to AOT compilation is the > warm-up overhead. I thought that you could achieve a similar effect as AOT > by starting up a program in Pypy, running it on a hardcoded workload to warm > it up, and then pause the process. Then when you want to run the program, > you fork the already warmed up process and run it on your desired input. > > Is this something that is possible to do with Pypy? > > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
