On Mon, Oct 1, 2012 at 7:54 AM, Antoine Pitrou wrote:
> On Sun, 30 Sep 2012 21:49:20 -0400
> Brett Cannon wrote:
> > > Note that Mako can use the Markupsafe library for faster operation.
> > > This will skew the result if one of your Pythons has Markupsafe
> > > installed and the other does not.
On Mon, Oct 1, 2012 at 3:44 AM, Maciej Fijalkowski wrote:
> On Mon, Oct 1, 2012 at 1:12 AM, Brett Cannon wrote:
> > I am presenting the talk "Python 3.3: Trust Me, It's Better Than 2.7" as
> > PyCon Argentina and Brasil (and US if they accept the talk). As part of
> that
> > talk I need to be ab
On Sun, 30 Sep 2012 21:49:20 -0400
Brett Cannon wrote:
> > Note that Mako can use the Markupsafe library for faster operation.
> > This will skew the result if one of your Pythons has Markupsafe
> > installed and the other does not.
> >
>
> Should probably have the benchmark print out a warning w
On Mon, Oct 1, 2012 at 1:12 AM, Brett Cannon wrote:
> I am presenting the talk "Python 3.3: Trust Me, It's Better Than 2.7" as
> PyCon Argentina and Brasil (and US if they accept the talk). As part of that
> talk I need to be able to benchmark Python 3.3 against 2.7 (both from tip)
> using the unl
On Mon, Oct 1, 2012 at 7:07 AM, Robert Collins
wrote:
> On Mon, Oct 1, 2012 at 2:35 PM, Steven D'Aprano wrote:
>> On Sun, Sep 30, 2012 at 07:12:47PM -0400, Brett Cannon wrote:
>>
>>> > python3 perf.py -T --basedir ../benchmarks -f -b py3k
>>> ../cpython/builds/2.7-wide/bin/python ../cpython/build
On Mon, Oct 1, 2012 at 2:35 PM, Steven D'Aprano wrote:
> On Sun, Sep 30, 2012 at 07:12:47PM -0400, Brett Cannon wrote:
>
>> > python3 perf.py -T --basedir ../benchmarks -f -b py3k
>> ../cpython/builds/2.7-wide/bin/python ../cpython/builds/3.3/bin/python3.3
>
>> ### call_method ###
>> Min: 0.491433
On Sun, Sep 30, 2012 at 8:28 PM, Antoine Pitrou wrote:
> On Sun, 30 Sep 2012 19:12:47 -0400
> Brett Cannon wrote:
> >
> > ### mako_v2 ###
> > Min: 0.137584 -> 0.287701: 2.09x slower
> > Avg: 0.140620 -> 0.293204: 2.09x slower
> > Significant (t=-296.14)
> > Stddev: 0.00243 -> 0.00272: 1.1195x la
On Sun, Sep 30, 2012 at 9:35 PM, Steven D'Aprano wrote:
> On Sun, Sep 30, 2012 at 07:12:47PM -0400, Brett Cannon wrote:
>
> > > python3 perf.py -T --basedir ../benchmarks -f -b py3k
> > ../cpython/builds/2.7-wide/bin/python ../cpython/builds/3.3/bin/python3.3
>
> > ### call_method ###
> > Min: 0.4
On Sun, Sep 30, 2012 at 07:12:47PM -0400, Brett Cannon wrote:
> > python3 perf.py -T --basedir ../benchmarks -f -b py3k
> ../cpython/builds/2.7-wide/bin/python ../cpython/builds/3.3/bin/python3.3
> ### call_method ###
> Min: 0.491433 -> 0.414841: 1.18x faster
> Avg: 0.493640 -> 0.416564: 1.19x fa
On Sun, Sep 30, 2012 at 8:14 PM, Gregory P. Smith wrote:
> Interesting results!
>
> Another data point for the benchmarks that would be interesting is memory
> consumption of the python process during the runs.
>
> In 3.3 a reasonable place to gather this would be to add a callback to the
> new g
On Sun, Sep 30, 2012 at 8:07 PM, Alexandre Vassalotti wrote:
>
>
> On Sun, Sep 30, 2012 at 4:50 PM, Brett Cannon wrote:
>
>> I accidentally left out the telco benchmark, which is bad since cdecimal
>> makes it just scream on Python 3.3 (and I verified with Python 3.2 that
>> this is an actual sp
On Sun, 30 Sep 2012 19:12:47 -0400
Brett Cannon wrote:
>
> ### mako_v2 ###
> Min: 0.137584 -> 0.287701: 2.09x slower
> Avg: 0.140620 -> 0.293204: 2.09x slower
> Significant (t=-296.14)
> Stddev: 0.00243 -> 0.00272: 1.1195x larger
Note that Mako can use the Markupsafe library for faster operation
Interesting results!
Another data point for the benchmarks that would be interesting is memory
consumption of the python process during the runs.
In 3.3 a reasonable place to gather this would be to add a callback to the
new gc.callbacks and save a snapshot of the process's memory usage before
ev
On Sun, Sep 30, 2012 at 4:50 PM, Brett Cannon wrote:
> I accidentally left out the telco benchmark, which is bad since cdecimal
> makes it just scream on Python 3.3 (and I verified with Python 3.2 that
> this is an actual speedup and not some silly screw-up like I initially had
> with spectral_no
I accidentally left out the telco benchmark, which is bad since cdecimal
makes it just scream on Python 3.3 (and I verified with Python 3.2 that
this is an actual speedup and not some silly screw-up like I initially had
with spectral_norm):
### telco ###
Min: 0.897108 -> 0.016880: 53.15x faster
Av
I am presenting the talk "Python 3.3: Trust Me, It's Better Than 2.7" as
PyCon Argentina and Brasil (and US if they accept the talk). As part of
that talk I need to be able to benchmark Python 3.3 against 2.7 (both from
tip) using the unladen benchmarks (which now include benchmarks from PyPy
that
16 matches
Mail list logo
