Re: [pypy-dev] Moving the project forward
On 31/08/11 10:12, Antonio Cuni wrote: I can setup a buildbot instance on speed.pypy.org, if you give me access to the machine. I propose that as a very first step, we just make speed.pypy.org a buildslave which depends on pypy's own buildmaster. This makes it very easy and fast to setup it, so we can have something running soon. sorry, of course I meant speed.python.org in the paragraph above! So, to recapitulate: as a first and fast solution, I propose to setup speed.python.org as a buildslave for PyPy's buildmaster. ciao, Anto ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
[pypy-dev] PyCon UK wants pypy
This is the message that got bounced. Since I now am admin this shouldn't happen any more. --- Forwarded Message Return-Path: funth...@gmail.com Delivery-Date: Wed Aug 31 10:47:05 2011 Return-Path: funth...@gmail.com Message-ID: cab-vkoqjdyboecwzo9mfxmmouzcoxjrrbbz2kezr7xmbbrl...@mail.gmail.com Subject: Fwd: PyPy at PyCon UK From: John Pinner funth...@gmail.com To: Laura Creighton l...@openend.se The bounced post... - -- Forwarded message -- From: John Pinner funth...@gmail.com Date: 30 August 2011 23:45 Subject: PyPy at PyCon UK To: pypy-dev@python.org Hello Guys, You should have heard that we are holding PyCon UK 2011 on 24th-25th September 2011 at Coventry, UK (about 25km from Birmingham where we held EP2009/EP2010). Details are on the wiki at http://pyconuk.net. It would be good to have a PyPy presence, at least a talk, maybe a Workshop, or better still a sprint. The new venue has excellent facilities, including really good internet access (typically 35 Mbits up and down). If you'd like to take part, please put things up on the wiki. If you want to hold a sprint, we could extend it either side of the conference days, to include Friday 23rd and/or Monday 26th September, but we need to know if you want to do this, and numbers of sprinters, this week to make sure we have the facilities booked and finance available. Best wishes, John - -- --- End of Forwarded Message ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
-On [20110831 02:57], Noah Kantrowitz (n...@coderanger.net) wrote: Yahr, I be here. I would really like to see this done under a config management system (I prefer Chef and thats been the plan so far unless there are heavy objections). In general no one should ever be changing things on any PSF server by hand if at all possible in the interests of disaster recovery, reproducibility, and some modicum of enforced documentation (even if that doc is just a Chef recipe). If Noah's going to pull this, being an Opscode guy, does it make sense for me to help out. I mean, he's the Chef guru here and I doubt there's little I can contribute then? -- Jeroen Ruigrok van der Werven asmodai(-at-)in-nomine.org / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | GPG: 2EAC625B Under this standard shalt thou conquer... ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
[pypy-dev] PyCon UK and PyPy
Hello Guys, You should have heard that we are holding PyCon UK 2011 on 24th-25th September 2011 at Coventry, UK (about 25km from Birmingham where we held EP2009/EP2010). Details are on the wiki at http://pyconuk.net. It would be good to have a PyPy presence, at least a talk, maybe a Workshop, or better still a sprint. The new venue has excellent facilities, including really good internet access (typically 35 Mbits up and down). If youd like to take part, please put things up on the wiki. If you want to hold a sprint, we could extend it either side of the conference days, to include Friday 23rd and/or Monday 26th September, but we need to know if you want to do this, and numbers of sprinters, this week to make sure we have the facilities booked and finance available. Best wishes, John -- ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Hacking at tarfile.py and gzip.py
Re-hi, On Wed, Aug 31, 2011 at 1:35 PM, Armin Rigo ar...@tunes.org wrote: If you do helpful performance fixes, they are probably helpful for CPython, too, and so they should go to the CPython issue tracker. ...or, I just saw this kind of check-in: pypy doesn't like adding empty strings. Instead of fixing it in tarfile.py, this is really an issue in PyPy: maybe the addition of an empty string and another string is not special-cased to just return the other string, as it would be in CPython. If so, then tarfile.py is just a real-life example of why it's a good idea, and we should fix PyPy's strings instead. A bientôt, Armin. ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Policy on Python 3 and Python 2 executable names
On Wed, Aug 31, 2011 at 12:13 AM, Armin Rigo ar...@tunes.org wrote: I suppose that we need to *have* a pypy3 first, before any conversation like that really makes sense. Last March this wasn't even being considered. Now it is maybe in some very draftish early planning stage. The idea is to be proactive in policy making instead of allowing the problem to be acute like with CPython. -Aaron DeVore ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Moving the project forward
I've put up a splash page for the project this AM: http://speed.python.org/ jesse ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] Moving the project forward
Hi all, though I took up on the task of installing a Codespeed instance myself, I didn't have time until now. This weekend I will definitely have a *lot* of time to work on this, so count on that task being done by then. The bitbucket issue tracker is a start (though a organization account would be better) and the splash page is great. So let's get started organizing things. Regarding the deployment strategy, it turns out I use Chef at work, so I am in full agreement with Noah here (yey!). Actually, I am the author of LittleChef (which we can use as a tool to execute Chef on the node). So, Configuration Management. I would propose that Noah starts the repo with the Chef cookbooks (preferably a complete LittleChef kitchen, but that is not a must :), and gets the main recipes (apache, django) going, while I create a cookbook for Codespeed. What do you think? The benchmark runner question is still open. We need to clarify that. Use the pypy runner? Tennessee's work? Regarding repositories and issues, we could maybe have a speed organization account (not sure on Bitbucket, you can do that in Github), where we have a wiki, issues, and runner + config management repo + other stuff. Cheers, Miquel 2011/8/31 Jesse Noller jnol...@gmail.com: I've put up a splash page for the project this AM: http://speed.python.org/ jesse ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
Oh, cool, so there will be an Opscode hosted account for the PSF, right? Then the Chef repo should be for the PSF. Maybe in a current account somewhere? What do you propose? Miquel 2011/8/31 Noah Kantrowitz n...@coderanger.net: Opscode has already agreed to donate a Hosted account as long we keep it under ~20 clients :-) I can hand out the info for it to anyone that wants. As for setting up the Chef repo, just remember we are trying to not manage this system in isolation and that it will be part of a bigger PSF infrastructure management effort. --Noah On Aug 31, 2011, at 11:34 AM, Miquel Torres wrote: Hi all, though I took up on the task of installing a Codespeed instance myself, I didn't have time until now. This weekend I will definitely have a *lot* of time to work on this, so count on that task being done by then. The bitbucket issue tracker is a start (though a organization account would be better) and the splash page is great. So let's get started organizing things. Regarding the deployment strategy, it turns out I use Chef at work, so I am in full agreement with Noah here (yey!). Actually, I am the author of LittleChef (which we can use as a tool to execute Chef on the node). So, Configuration Management. I would propose that Noah starts the repo with the Chef cookbooks (preferably a complete LittleChef kitchen, but that is not a must :), and gets the main recipes (apache, django) going, while I create a cookbook for Codespeed. What do you think? The benchmark runner question is still open. We need to clarify that. Use the pypy runner? Tennessee's work? Regarding repositories and issues, we could maybe have a speed organization account (not sure on Bitbucket, you can do that in Github), where we have a wiki, issues, and runner + config management repo + other stuff. Cheers, Miquel 2011/8/31 Jesse Noller jnol...@gmail.com: I've put up a splash page for the project this AM: http://speed.python.org/ jesse ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev ___ Speed mailing list sp...@python.org http://mail.python.org/mailman/listinfo/speed ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Re: [pypy-dev] [Speed] Moving the project forward
On Wed, Aug 31, 2011 at 11:34, Miquel Torres tob...@googlemail.com wrote: Hi all, though I took up on the task of installing a Codespeed instance myself, I didn't have time until now. This weekend I will definitely have a *lot* of time to work on this, so count on that task being done by then. The bitbucket issue tracker is a start (though a organization account would be better) and the splash page is great. So let's get started organizing things. [SNIP] Regarding repositories and issues, we could maybe have a speed organization account (not sure on Bitbucket, you can do that in Github), where we have a wiki, issues, and runner + config management repo + other stuff. The PyPy folk could answer this as they have their repo on bitbucket already. Else I guess we can just create a standalone account that represents the official speed.python.org account. ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
[pypy-dev] Here's a fun one...
This came up on an internal discussion, I thought it was fun, especially given that we all behave differently: Paste this into the REPL: class PS1(object): def __init__(self): self.count = 0 def __str__(self): self.count += 1 return %d % self.count import sys sys.ps1 = PS1() CPython - calls __str__ Jython - calls __repr__ IronPython - ignores ps1 PyPy - unsupported operand type for unary buffer: 'PS1' (note I don't necessarily have the latest versions for everyone) ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
[pypy-dev] djangobench performance
Hi all, As an experiment, I thought I'd test JKM's djangobench ( https://github.com/jacobian/djangobench) under pypy as a way of determining a (hopefully) more useful benchmark than the template-only django benchmark that's standard on speed.pypy.org and also to get an idea as to whether switching to pypy for production django apps could (currently) be a good idea. djangobench is designed to fairly comprehensively compare the performance of different aspects of differing versions of django in an effort to detect performance degradation/regression/etc. It's based on perf.py from the unladen swallow project, so it was fairly easy to crudely hack up to instead compare a single django version running under cpython 2.6 vs pypy 1.6. --- $ python -V Python 2.6.5 $ pypy -V Python 2.7.1 (d8ac7d23d3ec, Aug 17 2011, 11:51:19) [PyPy 1.6.0 with GCC 4.4.3] --- The results were a little surprising (and not in a good way): http://pastie.org/2463906 Based on the highly degraded performance (2 orders of magnitude in some cases) I'm guessing there's some sort of issue in the way I'm benchmarking things. Code can be found here: https://github.com/fennb/djangobench Environment is ubuntu 10.04 64bit running in a VM on a macbook pro. cpython was the current ubuntu binary package, pypy was 1.6 precompiled binary from pypy.org. It's quite possible memory size issues may have impacted some of the benchmarks (but not all). Any ideas as to why the performance drop-off would be so significant? Cheers, Fenn. ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
