Repost:
Okay, so all of a sudden there seem to be a *lot* of people looking at this. This was a long thread quickly, and I only just got up to speed with it. There are a lot of new names, and I don't know what existing skills, interest and territories exist. Apologies for any faux pas.
I would like to organise the list of tasks a bit more clearly if that is okay. I may be less familiar with the parts of this process than others, so I just want to get it down clearly.
What I've done: -- Clone the Python repo into /home/speedracer/cpython/cpython (updated to 2.7) -- Installed os packages to support a reasonable build. -- Built and installed python2.7 into /home/speedraver/cpython/27_bin
Presumably, people would like to be monitoring both PyPy and Cpython as they progress over time. This means some kind of auto runner which updates from the repo, re-runs the timings, and submits them to codespeed. I am unclear on whether there is a "clear winner" for this piece of technology.
List of Required Infrastructure on speed.python.org: -- A home for the cpython repo (check) -- An installed and running codespeed server (pending) -- A buildbot / automation for keeping up to date with the PyPy and cpython repos (???) -- Automation to execute a process which must (???) 1) Run the benchmarks 2) Submit results to codespeed
I would suggest that the codespeed server be installed into speedracer's home directory.
This must all be installable and configurable from Chef (which appears to me like Fabric, i.e. an automation tool for deployment and management of systems). This is not yet accomplished.
We also clearly need some kind of wiki documentation on what is going on, so that contributors (or just newbies like me) can figure out where things are at and what is going on. The bitbucket project is great, but the task titles are currently rather brief if someone isn't already totally up-to-speed on what is going on.
There appear to me to be two unresolved questions:
- What piece of technology should we use for a buildbot / build automation
- What piece of technology should we use for the benchmark runner?
I have no suggestions on (1), it's not a strong point for me.
As regards (2), I am ignorant to what others might already be using, except to say the landscape seems unclear and fractured to me. My work, benchmarker.py, is likely to be adaptable to our needs and I am more than happy to support the package so it can be applied here. As I understand it, the GSOC project was about the actual benchmarking functions, not so much about automation and support for managing the results of benchmarking. If an already-working alternative to benchmarker.py exists and makes more sense to use, then that is fine by me. I would still like to help out to learn more about benchmarking.
The main issue with me as a contributor will be time. I have a full plate as a result of Real Life, so I will sometimes go dark for a week or so. However, I'm motivated and interested, and can put in a few hours a week most weeks.
Do I have this right? Is that a reasonable description of the work breakdown? Do we have clear names against tasks so that co-ordination can be done through those people (rather than via the whole list)?
Regards, -Tennessee
On Mon, Sep 26, 2011 at 5:13 AM, Jesse Noller jnoller@gmail.com wrote:
We need someone to do it. Are there instructions everywhere
On Sep 25, 2011, at 1:55 PM, Miquel Torres tobami@googlemail.com wrote:
So, is anyone working on the benchmark runner part? or should we "resign" that task, or look for other possibilities?
Miquel
2011/9/14 Miquel Torres tobami@googlemail.com:
Ok, great!
I can help out by giving you the rough recipe outline:
include_recipe "apache2::mod_wsgi"
easy_install "codespeed"
web_app "codespeed" do server_name node['hostname'] server_aliases [node['fqdn'], "speed.python.org"] template "speed.conf.erb" docroot "/home/tobami/speed/" # though we can change that end
As a base for the custom template you can take the current /etc/apache2/sites-enables/codespeed
Now this is were things get more complicated. The Django project is under /home/tobami/speed/, with www-data permissions (so you can copy anything). The speed/templates/ contains the basic templates for the views. and the content of sitestatic was created with "./manage.py collectstatic".
So this last part will need some execute block or similar. For anything else you need just ask and I'll help!
Miquel
PS: Python logo is up ;-)
2011/9/14 Noah Kantrowitz noah@coderanger.net:
No worries, I'll just take a look at the box and document what you did into recipes as we are doing with the other PSF machines :-) Thanks for getting it up so quickly!
--Noah
On Sep 14, 2011, at 11:21 AM, Miquel Torres wrote:
Hi Noah,
I didn't use any recipes for it, was more of a one-off. Would of course like to have a cookbook and run_list for it all, but I am not there yet.
Miquel
2011/9/13 Noah Kantrowitz noah@coderanger.net:
Just wanted to poke about this again post-weekend :-)
--Noah
On Sep 11, 2011, at 3:39 PM, Noah Kantrowitz wrote:
> Did the recipes for it get posted somewhere or was this a one-off by hand? I've started building some basic Chef infra for all PSF machines and can easily combine it with some more specific stuffs for codespeed :-) > > --Noah > > On Sep 11, 2011, at 2:15 AM, Miquel Torres wrote: > >> Hi all, >> >> it took longer than expected, but speed.python.org points now to a >> proper Codespeed instance! >> The admin media does not yet load properly, need to fix that yet. >> >> Anyway, for further configuring, we need to define an environment. I >> looks like we are going to directly test on that big server, bare >> metal. Should we call it by a name? or just 24-Core-monster? >> >> As to the welcome page, if you prefer we can put it back in, with a >> link to a subdomain or other URL were we keep Codespeed as long as we >> are still setting up thing, and only go live when we are finished and >> want to announce. >> >> What do you think? >> Miquel >> _______________________________________________ >> Speed mailing list >> Speed@python.org >> http://mail.python.org/mailman/listinfo/speed > > _______________________________________________ > Speed mailing list > Speed@python.org > http://mail.python.org/mailman/listinfo/speed
Speed mailing list Speed@python.org http://mail.python.org/mailman/listinfo/speed
Speed mailing list Speed@python.org http://mail.python.org/mailman/listinfo/speed
--
Tennessee Leeuwenburg http://myownhat.blogspot.com/ "Don't believe everything you think"