That's a great tip, :-). Just done with an experiment, and PyPy2 5.4.1-alpha0
cut down build time by 27% compared with CPython2.7.6
Thanks!
Peter
-Original Message-
From: Yury V. Zaytsev [mailto:y...@shurup.com]
Sent: Wednesday, September 07, 2016 1:08 PM
To: Wang, Peter Xihong
Cc:
On 07/09/16 22:07, Yury V. Zaytsev wrote:
>> On 30/08/2016 9:53 am, "Wang, Peter Xihong"
>> wrote:
>>
>> By default, it appears most of the time during the build/compile
>> process, only 1 single CPU core is busy, signaling missing of parallel
>> compiling. Is there any best known practice to mak
On 30/08/2016 9:53 am, "Wang, Peter Xihong"
wrote:
By default, it appears most of the time during the build/compile
process, only 1 single CPU core is busy, signaling missing of parallel
compiling. Is there any best known practice to make it faster?
Now that I think about it, there is yet
On Wed, 7 Sep 2016, Wang, Peter Xihong wrote:
We did notice fancy screen output during the build process to
demonstrate the build progress, and I am wondering if a build option
could be made to disable the output, which may save some valuable build
time. Just a thought.
I understand that you
On Tue, 30 Aug 2016, William ML Leslie wrote:
> On 30/08/2016 9:53 am, "Wang, Peter Xihong"
> wrote:
>
> By default, it appears most of the time during the build/compile
> process, only 1 single CPU core is busy, signaling missing of parallel
> compiling. Is there any best known practice to
HI Yury,
Thanks for clarifying on this.
Also want to take this opportunity to thank William for the initial answer.
We did notice fancy screen output during the build process to demonstrate the
build progress, and I am wondering if a build option could be made to disable
the output, which may
