I've gotten Noah Kantrowitz on here, he's doing some other infrastructure stuff for the PSF, and would like to include <a href="http://speed.python.org">speed.python.org</a> in the proper organization of the machines, rather than ad-hoc "everyone installs what they think it needs" :)<div>
<br></div><div>Alex<br><br><div class="gmail_quote">On Tue, Aug 30, 2011 at 8:28 PM, Jesse Noller <span dir="ltr"><<a href="mailto:jnoller@gmail.com">jnoller@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
(Re-sending intentionally - I wasn't subbed to pypy-dev and got rejected)<br>
<div><div></div><div class="h5"><br>
On Tue, Aug 30, 2011 at 8:22 PM, Jesse Noller <<a href="mailto:jnoller@gmail.com">jnoller@gmail.com</a>> wrote:<br>
> Here's a summary (nicely put together by Nick Coghlan):<br>
><br>
> - OSU/OSL have set up the machine itself (details in the July list archives)<br>
> - I am the machine admin (I have root)<br>
> - Tennessee and Miquel are working on getting codespeed up and running<br>
><br>
> - I and Maciej are already too busy to handle the coordination/admin<br>
> side of things<br>
><br>
> I just added the "speedracer" account - a common account to setup<br>
> things as needed. Currently, I don't see activity from Miquel on<br>
> setting up the codespeed instance. I know Tennessee has been looking<br>
> at setting up the runner.<br>
><br>
> What we need is this, very simply:<br>
><br>
> 1 - A working, running codespeed instance installed<br>
> 2 - Benchmark runner(s) setup and going - for PyPy and CPython 2.x<br>
> since the benchmarks don't run on Python 3 yet.<br>
><br>
><br>
> Other needs/notes:<br>
> - a project issue tracker doesn't appear to exist yet (needs to be done)<br>
> - a better 'placeholder/about' page would be useful that offered links to:<br>
> - the <a href="mailto:speed@python.org">speed@python.org</a> mailing list signup page<br>
> - the issue tracker (once it exists)<br>
> - the codespeed repo<br>
><br>
> Ideally, the front landing page would end up looking like:<br>
> <a href="http://speed.pypy.org/" target="_blank">http://speed.pypy.org/</a><br>
><br>
> - the aim is to eventually have the web front end running on different<br>
> (but still OSU/OSL hosted) hardware, although that likely isn't<br>
> critical right now<br>
><br>
> - the current 5 GB /tmp size may be a problem for PyPy<br>
><br>
> Where do we go from here - I can not be the one to keep pestering the<br>
> group to make forward progress. On behalf of the PSF, and the CPython<br>
> and PyPy teams, I got us a donated platform for running these shared,<br>
> common benchmarks. Right now we have a 10,000$+ paper weight taking<br>
> rack space in OSU/OSL.<br>
><br>
> I need someone to take lead on this and get the project moving forward<br>
> - as a reminder, here was the original proposal I made to the board,<br>
> after PyCon 2011:<br>
><br>
> """<br>
> Coming out of the PyCon VM and language summits, it was commonly<br>
> agreed that PyPy, CPython, IronPython and Jython should strive to move<br>
> to a common set of benchmarks and a single performance-oriented site.<br>
> This was agreed upon by the maintainers present at the conference, and<br>
> included leads from all of the major implementations. This project<br>
> would be lead by the various VM development teams, and based around<br>
> the Unladen Swallow/PyPy benchmark suite. The site would be derived<br>
> from:<br>
><br>
> <a href="http://speed.pypy.org/" target="_blank">http://speed.pypy.org/</a><br>
><br>
> There are already GSOC students potentially lined up to work on<br>
> porting the test suite to Python 3!<br>
><br>
> There, of course, is the requirement that we have:<br>
><br>
> 1> A machine<br>
> 2> Hosting for that machine<br>
><br>
> And I took the job of finding both. As the OSU/OSL [1] has come up<br>
> several times in discussions about free, monitored hosting, I felt<br>
> that now would be the time to float the trial balloon and start a<br>
> continuing relationship with the OSU/OSL team. I got to speak with<br>
> some of the team at PyCon, and I was quite impressed with their<br>
> enthusiasm and willingness to help out.<br>
> """<br>
><br>
> I need help from everyone to get this up and running: the PyPy team is<br>
> most familiar with the <a href="http://speed.pypy.org/codespeed" target="_blank">speed.pypy.org/codespeed</a> system. If we could<br>
> get a dump of what needs to be done to get things setup, that may help<br>
> get more hands involved.<br>
><br>
> I am feeling personally responsible that this has not been moving<br>
> forward - I need your help to get this up and running for the<br>
> betterment of CPython and PyPy. This project benefits both projects,<br>
> and Python in general immensely.<br>
><br>
> Once up and running, this system will be prominently placed on the<br>
> Python.org home page, and be used by potential users to help select<br>
> and evaluate their Python runtime.<br>
><br>
> Jesse<br>
><br>
_______________________________________________<br>
</div></div>pypy-dev mailing list<br>
<a href="mailto:pypy-dev@python.org">pypy-dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/pypy-dev" target="_blank">http://mail.python.org/mailman/listinfo/pypy-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>"I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)<br>"The people's good is the highest law." -- Cicero<br>
<br>
</div>