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
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 about it
at https://01.org/lp/blog/0-day-challenge-what-pulse-interne
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 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:
>
12 matches
Mail list logo
