[Python-Dev] Avoiding CPython performance regressions
Hi python-dev, I've seen that on and off CPython had attempts to measure benchmarks over time to avoid performance regressions (i.e.: https://speed.python.org), but had nothing concrete so far, so, I ended up creating a hosted service for that (https://www.speedtin.com) and I'd like to help in setting up a structure to run the benchmarks from https://hg.python.org/benchmarks/ and properly upload them to SpeedTin (if CPython devs are Ok with that) -- note that I don't really have server to run the benchmarks, only to host the data (but https://speed.python.org seems to indicate that such a server is available...). There's a sample report at: https://www.speedtin.com/reports/1_CPython27x_Performance_Over_Time/ (it has real data from running using the PyPy benchmarks as I only discovered about the benchmarks from https://hg.python.org/benchmarks/ later on -- also, it doesn't seem to support Python 3 right now, so, it's probably not that useful for the current Python dev, but it does have some nice insight on CPython 2.7.x performance over time). Later on, the idea is being able to compare across different Python implementations which use the same benchmark set... (although that needs other implementations to also post to the data to SpeedTin). Note that uploading the data to SpeedTin should be pretty straightforward (by using https://github.com/fabioz/pyspeedtin, so, the main issue would be setting up o machine to run the benchmarks). Best Regards, Fabio ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Avoiding CPython performance regressions
On Mon, 30 Nov 2015 09:02:12 -0200, Fabio Zadrozny wrote: > Note that uploading the data to SpeedTin should be pretty straightforward > (by using https://github.com/fabioz/pyspeedtin, so, the main issue would be > setting up o machine to run the benchmarks). Thanks, but Zach almost has this working using codespeed (he's still waiting on a review from infrastructure, I think). The server was not in fact running; a large part of what Zach did was to get that server set up. I don't know what it would take to export the data to another consumer, but if you want to work on that I'm guessing there would be no objection. And I'm sure there would be no objection if you want to get involved in maintaining the benchmark server! There's also an Intel project posted about here recently that checks individual benchmarks for performance regressions and posts the results to python-checkins. --David ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Help with a book
Thanks to everyone who has offered to look at and edit my book. I have enough help now, so I won't be taking anymore requests. On Wed, Nov 25, 2015 at 2:31 PM, Jacob Zimmerman wrote: > Hello Python Developers! > > I'm writing a book about descriptors, and I'm hoping to make it a > comprehensive guide, covering just about everything there is to know about > descriptors, including many tips to get past certain knowledge barriers and > how to avoid certain pitfalls. I'm hoping for it to become the definitive > guide for those who want to really understand descriptors. Raymond's > Descriptor HowTo Guide is great, but focused. I want to expand on what that > guide teaches. > > Anyway, I am currently reading through my initial rough draft and making > corrections for a revised draft. Once I'm done with that, I'd like a few > volunteers to read through it. First, to find spelling, grammatical, or > consistency mistakes, though those should be few in number, but also to > give input as to whether something seems too repetitive, if some more > information should be given in a spot, and if I'm even blatantly wrong > about anything (hopefully not). > > Anyone who helps will be able to receive a free ebook of the final copy as > well as mention in the Special Thanks. > > I appreciate any help anyone can give to assist in making this book as > great as it can be. > > Thanks, > Jacob Zimmerman > > Twitter: @jacobz_20 > Blog: http://programmingideaswithjake.wordpress.com > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Avoiding CPython performance regressions
On 11/30/15, 5:52 AM, "Python-Dev on behalf of R. David Murray" wrote: > >There's also an Intel project posted about here recently that checks >individual benchmarks for performance regressions and posts the results >to python-checkins. The description of the project is at https://01.org/lp - Python results are indeed sent daily to python-checkins. (No results for Nov 30 and Dec 1 due to Romania National Day holiday!) There is also a graphic dashboard at http://languagesperformance.intel.com/ Dave ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)
On Nov 27, 2015, at 04:04 PM, Nick Coghlan wrote: >New draft pushed: https://hg.python.org/peps/rev/f602a47ea795 > >This is a significant rewrite that switches the PEP to a Standards Track PEP >proposing two new features for 2.7.12+: an "ssl._verify_https_certificates()" >configuration function, and a "PYTHONHTTPSVERIFY" environment variable >(although writing them together like that makes me wonder if the latter >should now be "PYTHONVERIFYHTTPS" instead). Thanks for this, and +1 on Stephen's suggested name change (which you've already pushed). Two comments: the PEP still describes the configuration file implementation. Is this slated for 2.7.12 also? If not, should it just be dropped from the PEP? I'd mildly prefer no default value for `enable` in _https_verify_certificates(). I'd have preferred a keyword-only argument, but of course this is Python 2. Instead, I'd like to force passing True or False (and document using `enable=True` or `enable=False`) and not rely on a default argument. But I'm only +0 on that detail. Cheers, -Barry pgpkeUFzn5kLf.pgp Description: OpenPGP digital signature ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
