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
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
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
+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
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
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
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
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
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
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
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
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
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
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:
>
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
On Wed, Jul 29, 2015 at 9:40 AM Catalin G. Manciu <
catalin.gabriel.man...@intel.com>
[SNIP -- stuff came back as visible HTML; hopefully I didn't miss something]
>
>
> Thank you for your feedback! We value the community’s input and we would
> like to provide the most relevant results in our autom
Brett Cannon python.org> writes:
>
>
> Should we discuss of these are the benchmarks we want daily reports on
(you can see what the benchmark suite has at
https://hg.python.org/benchmarks/file/2979f5ce6a0c/perf.py#l2243 )? I
personally would prefer dropping pybench and replacing it with a st
Hi,
I don't know if it's related but at EuroPython at saw a new website
which can also help:
http://pybenchmarks.org/
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mai
Should we discuss of these are the benchmarks we want daily reports on (you
can see what the benchmark suite has at
https://hg.python.org/benchmarks/file/2979f5ce6a0c/perf.py#l2243 )? I
personally would prefer dropping pybench and replacing it with a startup
measurement.
On Fri, Jul 24, 2015, 07:2
On 24 July 2015 at 23:55, Serhiy Storchaka wrote:
> On 24.07.15 15:34, lp_benchmark_robot wrote:
>> The community's feedback is very important for us. For any questions,
>> comments or suggestions you can also contact us on our mailing list
>> l...@lists.01.org. You can also check our website: htt
On 24.07.15 15:34, lp_benchmark_robot wrote:
Hi Internals,
This is the first message from Intel's language optimization team.
We would like to provide the Python internals developer community
with a daily service which will monitor latest committed patches
performance regressions against well kn
Hi Internals,
This is the first message from Intel's language optimization team.
We would like to provide the Python internals developer community
with a daily service which will monitor latest committed patches
performance regressions against well known workloads.
Our aim is to run a multitude o
Oops, I wanted to send the patch to myself, not to the python-dev
mailing list, sorry :-)
(It's a set of patch to try to optimize the tracemalloc module.)
Victor
2013/9/18 Victor Stinner :
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mai
benchmark.patch
Description: Binary data
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Hi,
as Antoine pointed out in the corresponding issue
(http://bugs.python.org/issue14757#msg160870), measuring/assessing
real-world performance of my patch would be interesting. I mentioned
that I am not aware of any relevant Python 3 program/application to
report numbers for (but guess that the s
25 matches
Mail list logo
