On Tue, Jun 10, 2014 at 9:30 AM, Steve Dower
wrote:
>
> I ran a quick test with profile-guided optimization (PGO, pronounced
> "pogo"), which has supposedly been improved since VC9, and saw a very
> unscientific 20% speed improvement on pybench.py and 10% size reduction in
> python35.dll. I'm not
Martin v. Löwis wrote:
> Am 10.06.14 18:30, schrieb Steve Dower:
>> I ran a quick test with profile-guided optimization (PGO, pronounced
>> "pogo"), which has supposedly been improved since VC9, and saw a very
>> unscientific 20% speed improvement on pybench.py and 10% size
>> reduction in python35
Am 10.06.14 18:30, schrieb Steve Dower:
> I ran a quick test with profile-guided optimization (PGO, pronounced
> "pogo"), which has supposedly been improved since VC9, and saw a very
> unscientific 20% speed improvement on pybench.py and 10% size
> reduction in python35.dll. I'm not sure what we us
2014-06-10 18:30 GMT+02:00 Steve Dower :
> I ran a quick test with profile-guided optimization (PGO, pronounced "pogo"),
> which has supposedly been improved since VC9, and saw a very unscientific 20%
> speed improvement on pybench.py and 10% size reduction in python35.dll. I'm
> not sure what w
> Antoine Pitrou wrote:
> Le 10/06/2014 12:30, Steve Dower a écrit :
>>
>> I ran a quick test with profile-guided optimization (PGO, pronounced
>> "pogo"), which has supposedly been improved since VC9, and saw a very
>> unscientific 20% speed improvement on pybench.py and 10% size reduction in
>> p
Le 10/06/2014 12:30, Steve Dower a écrit :
I ran a quick test with profile-guided optimization (PGO, pronounced
"pogo"), which has supposedly been improved since VC9, and saw a very
unscientific 20% speed improvement on pybench.py and 10% size reduction
in python35.dll. I'm not sure what we use
