Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-18 Thread R. David Murray
On 17 Nov 2015, at 21:22, Stewart, David C wrote: > On 11/17/15, 10:40 AM, "Python-Dev on behalf of R. David Murray" > rdmur...@bitdance.com> wrote: >> >> I suppose that for this to have maximum effect someone would have to >> specifically be paying attention to performance and figuring out why

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-17 Thread Stephen J. Turnbull
Stewart, David C writes: > Note: PGO is not the default way to build Python because it is > relatively slow to compile it that way. (I think it should be the > default). +1 Slow-build-fast-run should be the default if you're sure the optimization works. Only developers are likely to run a gi

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-17 Thread Popa, Stefan A
Hi Python community, Thank you for your feedback! We will look into this and come up with an e-mail format proposal in the following days. Best regards, -- Stefan A. POPA Software Engineering Manager System Technologies and Optimization Division Software Services Group, Intel Romania > On 17 N

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-17 Thread Stewart, David C
+Stefan (owner of the 0-day lab) On 11/17/15, 10:40 AM, "Python-Dev on behalf of R. David Murray" wrote: >On Mon, 16 Nov 2015 23:37:06 +, "Stewart, David C" > wrote: >> Last June we started publishing a daily performance report of the latest >> Python tip against the previous day's run

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-17 Thread R. David Murray
On Mon, 16 Nov 2015 23:37:06 +, "Stewart, David C" wrote: > Last June we started publishing a daily performance report of the latest > Python tip against the previous day's run and some established synch point. > We mail these to the community to act as a "canary in the coal mine." I wrote

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Stewart, David C
on Date: Monday, November 16, 2015 at 12:18 PM To: python-dev Subject: [Python-Dev] Benchmark results across all major Python implementations I gave the opening keynote at PyCon CA and then gave the same talk at PyData NYC on the various interpreters of Python (Jupyter notebook of my presentation

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Jim Baker
Brett, Very cool, I'm glad to see that Jython's performance was competitive under most of these benchmarks. I would also be interested in joining the proposed mailing list. re elementtree - I assume the benchmarking is usually done with cElementTree. However Jython currently lacks a Java equivale

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Tim Golden
On 16/11/2015 22:23, Zachary Ware wrote: On Mon, Nov 16, 2015 at 3:38 PM, Brian Curtin wrote: On Monday, November 16, 2015, Brett Cannon wrote: Hi Brett Any thoughts on improving the benchmark set (I think all of {cpython,pypy,pyston} introduced new benchmarks to the set). We should pr

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Zachary Ware
On Mon, Nov 16, 2015 at 3:38 PM, Brian Curtin wrote: > On Monday, November 16, 2015, Brett Cannon wrote: >>> >>> Hi Brett >>> >>> Any thoughts on improving the benchmark set (I think all of >>> {cpython,pypy,pyston} introduced new benchmarks to the set). >> >> >> We should probably start a maili

[Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Brian Curtin
On Monday, November 16, 2015, Brett Cannon > wrote: > > > On Mon, 16 Nov 2015 at 12:24 Maciej Fijalkowski wrote: > >> Hi Brett >> >> Any thoughts on improving the benchmark set (I think all of >> {cpython,pypy,pyston} introduced new benchmarks to the set). >> > > We should probably start a mailin

[Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Brian Curtin
On Monday, November 16, 2015, Brett Cannon > wrote: > > > On Mon, 16 Nov 2015 at 12:24 Maciej Fijalkowski wrote: > >> Hi Brett >> >> Any thoughts on improving the benchmark set (I think all of >> {cpython,pypy,pyston} introduced new benchmarks to the set). >> > > We should probably start a mailin

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Brett Cannon
On Mon, 16 Nov 2015 at 12:24 Maciej Fijalkowski wrote: > Hi Brett > > Any thoughts on improving the benchmark set (I think all of > {cpython,pypy,pyston} introduced new benchmarks to the set). > We should probably start a mailing list and finally hash out a common set of benchmarks that we all a

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread R. David Murray
On Mon, 16 Nov 2015 21:23:49 +0100, Maciej Fijalkowski wrote: > Any thoughts on improving the benchmark set (I think all of > {cpython,pypy,pyston} introduced new benchmarks to the set). > "speed.python.org" becoming a thing is generally stopped on "noone > cares enough to set it up". Actually, w

Re: [Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Maciej Fijalkowski
Hi Brett Any thoughts on improving the benchmark set (I think all of {cpython,pypy,pyston} introduced new benchmarks to the set). "speed.python.org" becoming a thing is generally stopped on "noone cares enough to set it up". Cheers, fijal On Mon, Nov 16, 2015 at 9:18 PM, Brett Cannon wrote: >

[Python-Dev] Benchmark results across all major Python implementations

2015-11-16 Thread Brett Cannon
I gave the opening keynote at PyCon CA and then gave the same talk at PyData NYC on the various interpreters of Python (Jupyter notebook of my presentation can be found at bit.ly/pycon-ca-keynote; no video yet). I figured people here might find the benchmark numbers interesting so I'm sharing the l