From jnoller at gmail.com Thu Aug 18 19:41:35 2011 From: jnoller at gmail.com (Jesse Noller) Date: Thu, 18 Aug 2011 13:41:35 -0400 Subject: [Speed] Pinging the group Message-ID: I would like to see the speed machine see good use; has anyone freed any time to setup codespeed or anything else we need to move forward? From tobami at googlemail.com Sat Aug 20 22:16:18 2011 From: tobami at googlemail.com (Miquel Torres) Date: Sat, 20 Aug 2011 22:16:18 +0200 Subject: [Speed] Pinging the group In-Reply-To: References: Message-ID: Hi Jesse, setting up codespeed is no problem, but is there any kind of benchmark runner already? 2011/8/18 Jesse Noller : > I would like to see the speed machine see good use; has anyone freed > any time to setup codespeed or anything else we need to move forward? > _______________________________________________ > Speed mailing list > Speed at python.org > http://mail.python.org/mailman/listinfo/speed > From jnoller at gmail.com Sat Aug 20 22:19:57 2011 From: jnoller at gmail.com (Jesse Noller) Date: Sat, 20 Aug 2011 16:19:57 -0400 Subject: [Speed] Pinging the group In-Reply-To: References: Message-ID: The goal was to run the same thing that runs speed.PyPy for starters - PyPy compared to CPython 2.x on the benchmarks would be a good start On Aug 20, 2011, at 4:16 PM, Miquel Torres wrote: > Hi Jesse, > > setting up codespeed is no problem, but is there any kind of benchmark > runner already? > > > 2011/8/18 Jesse Noller : >> I would like to see the speed machine see good use; has anyone freed >> any time to setup codespeed or anything else we need to move forward? >> _______________________________________________ >> Speed mailing list >> Speed at python.org >> http://mail.python.org/mailman/listinfo/speed >> From tleeuwenburg at gmail.com Wed Aug 24 06:55:15 2011 From: tleeuwenburg at gmail.com (Tennessee Leeuwenburg) Date: Wed, 24 Aug 2011 14:55:15 +1000 Subject: [Speed] Pinging the group In-Reply-To: References:

Message-ID: Hi all, I'm more than happy to lend some effort here if the task is straightforward enough for a newcomer to PyPy to achieve. Cheers, -T On Sun, Aug 21, 2011 at 6:19 AM, Jesse Noller wrote: > The goal was to run the same thing that runs speed.PyPy for starters - PyPy compared to CPython 2.x on the benchmarks would be a good start > > On Aug 20, 2011, at 4:16 PM, Miquel Torres wrote: > >> Hi Jesse, >> >> setting up codespeed is no problem, but is there any kind of benchmark >> runner already? >> >> >> 2011/8/18 Jesse Noller : >>> I would like to see the speed machine see good use; has anyone freed >>> any time to setup codespeed or anything else we need to move forward? >>> _______________________________________________ >>> Speed mailing list >>> Speed at python.org >>> http://mail.python.org/mailman/listinfo/speed >>> > _______________________________________________ > Speed mailing list > Speed at python.org > http://mail.python.org/mailman/listinfo/speed > -- -------------------------------------------------- Tennessee Leeuwenburg http://myownhat.blogspot.com/ "Don't believe everything you think" From jnoller at gmail.com Wed Aug 24 16:00:38 2011 From: jnoller at gmail.com (Jesse Noller) Date: Wed, 24 Aug 2011 10:00:38 -0400 Subject: [Speed] Pinging the group In-Reply-To: References:

Message-ID: I've given Miquel privileges to install the initial codespeed deployment - the initial goals are really simple: 1> Deploy codespeed "as is" running pypy and cpython benchmarks[1] 2> Work from there - show how CPython has evolved over time (just like the pypy charts), etc. Modifying the benchmark suite/etc is out of scope for initial deployment - the benchmarks as they sit today are an excellent jumping off point. We can work on improvements from there. Miquel - is there a way Tennessee can help us get up and toddling? [1] http://speed.pypy.org/ On Wed, Aug 24, 2011 at 12:55 AM, Tennessee Leeuwenburg wrote: > Hi all, > > I'm more than happy to lend some effort here if the task is > straightforward enough for a newcomer to PyPy to achieve. > > Cheers, > -T > > On Sun, Aug 21, 2011 at 6:19 AM, Jesse Noller wrote: >> The goal was to run the same thing that runs speed.PyPy for starters - PyPy compared to CPython 2.x on the benchmarks would be a good start >> >> On Aug 20, 2011, at 4:16 PM, Miquel Torres wrote: >> >>> Hi Jesse, >>> >>> setting up codespeed is no problem, but is there any kind of benchmark >>> runner already? >>> >>> >>> 2011/8/18 Jesse Noller : >>>> I would like to see the speed machine see good use; has anyone freed >>>> any time to setup codespeed or anything else we need to move forward? >>>> _______________________________________________ >>>> Speed mailing list >>>> Speed at python.org >>>> http://mail.python.org/mailman/listinfo/speed >>>> >> _______________________________________________ >> Speed mailing list >> Speed at python.org >> http://mail.python.org/mailman/listinfo/speed >> > > > > -- > -------------------------------------------------- > Tennessee Leeuwenburg > http://myownhat.blogspot.com/ > "Don't believe everything you think" > From tobami at googlemail.com Wed Aug 24 20:51:55 2011 From: tobami at googlemail.com (Miquel Torres) Date: Wed, 24 Aug 2011 20:51:55 +0200 Subject: [Speed] Pinging the group In-Reply-To: References:

Message-ID: hi Tennessee, as I am going to set up the Codespeed instance, you could try to configure the environment so that cpython benchmarks can be run (for the benchmarks pypy uses). Then we can configure the runner, and connect it to Codespeed. Miquel 2011/8/24 Jesse Noller : > I've given Miquel privileges to install the initial codespeed > deployment - the initial goals are really simple: > > 1> Deploy codespeed "as is" running pypy and cpython benchmarks[1] > 2> Work from there - show how CPython has evolved over time (just like > the pypy charts), etc. > > Modifying the benchmark suite/etc is out of scope for initial > deployment - the benchmarks as they sit today are an excellent jumping > off point. We can work on improvements from there. > > Miquel - is there a way Tennessee can help us get up and toddling? > > [1] http://speed.pypy.org/ > > > > On Wed, Aug 24, 2011 at 12:55 AM, Tennessee Leeuwenburg > wrote: >> Hi all, >> >> I'm more than happy to lend some effort here if the task is >> straightforward enough for a newcomer to PyPy to achieve. >> >> Cheers, >> -T >> >> On Sun, Aug 21, 2011 at 6:19 AM, Jesse Noller wrote: >>> The goal was to run the same thing that runs speed.PyPy for starters - PyPy compared to CPython 2.x on the benchmarks would be a good start >>> >>> On Aug 20, 2011, at 4:16 PM, Miquel Torres wrote: >>> >>>> Hi Jesse, >>>> >>>> setting up codespeed is no problem, but is there any kind of benchmark >>>> runner already? >>>> >>>> >>>> 2011/8/18 Jesse Noller : >>>>> I would like to see the speed machine see good use; has anyone freed >>>>> any time to setup codespeed or anything else we need to move forward? >>>>> _______________________________________________ >>>>> Speed mailing list >>>>> Speed at python.org >>>>> http://mail.python.org/mailman/listinfo/speed >>>>> >>> _______________________________________________ >>> Speed mailing list >>> Speed at python.org >>> http://mail.python.org/mailman/listinfo/speed >>> >> >> >> >> -- >> -------------------------------------------------- >> Tennessee Leeuwenburg >> http://myownhat.blogspot.com/ >> "Don't believe everything you think" >> > From tleeuwenburg at gmail.com Wed Aug 24 23:45:22 2011 From: tleeuwenburg at gmail.com (Tennessee Leeuwenburg) Date: Thu, 25 Aug 2011 07:45:22 +1000 Subject: [Speed] Pinging the group In-Reply-To: References:

Message-ID: Can do... I'll need a login. On 25/08/2011 4:51 AM, "Miquel Torres" wrote: > hi Tennessee, > > as I am going to set up the Codespeed instance, you could try to > configure the environment so that cpython benchmarks can be run (for > the benchmarks pypy uses). Then we can configure the runner, and > connect it to Codespeed. > > Miquel > > > 2011/8/24 Jesse Noller : >> I've given Miquel privileges to install the initial codespeed >> deployment - the initial goals are really simple: >> >> 1> Deploy codespeed "as is" running pypy and cpython benchmarks[1] >> 2> Work from there - show how CPython has evolved over time (just like >> the pypy charts), etc. >> >> Modifying the benchmark suite/etc is out of scope for initial >> deployment - the benchmarks as they sit today are an excellent jumping >> off point. We can work on improvements from there. >> >> Miquel - is there a way Tennessee can help us get up and toddling? >> >> [1] http://speed.pypy.org/ >> >> >> >> On Wed, Aug 24, 2011 at 12:55 AM, Tennessee Leeuwenburg >> wrote: >>> Hi all, >>> >>> I'm more than happy to lend some effort here if the task is >>> straightforward enough for a newcomer to PyPy to achieve. >>> >>> Cheers, >>> -T >>> >>> On Sun, Aug 21, 2011 at 6:19 AM, Jesse Noller wrote: >>>> The goal was to run the same thing that runs speed.PyPy for starters - PyPy compared to CPython 2.x on the benchmarks would be a good start >>>> >>>> On Aug 20, 2011, at 4:16 PM, Miquel Torres wrote: >>>> >>>>> Hi Jesse, >>>>> >>>>> setting up codespeed is no problem, but is there any kind of benchmark >>>>> runner already? >>>>> >>>>> >>>>> 2011/8/18 Jesse Noller : >>>>>> I would like to see the speed machine see good use; has anyone freed >>>>>> any time to setup codespeed or anything else we need to move forward? >>>>>> _______________________________________________ >>>>>> Speed mailing list >>>>>> Speed at python.org >>>>>> http://mail.python.org/mailman/listinfo/speed >>>>>> >>>> _______________________________________________ >>>> Speed mailing list >>>> Speed at python.org >>>> http://mail.python.org/mailman/listinfo/speed >>>> >>> >>> >>> >>> -- >>> -------------------------------------------------- >>> Tennessee Leeuwenburg >>> http://myownhat.blogspot.com/ >>> "Don't believe everything you think" >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From tleeuwenburg at gmail.com Tue Aug 30 08:54:47 2011 From: tleeuwenburg at gmail.com (Tennessee Leeuwenburg) Date: Tue, 30 Aug 2011 16:54:47 +1000 Subject: [Speed] Pinging the group In-Reply-To: References:

Message-ID: Right... so I have my login working. I could do this in my own username, but can I suggest a shared user for working in, to avoid any dependencies on some particular person's account? I'm happy to create a "worker" user for this purpose. Alternatively, is there some other way people would prefer to get things set up? I should be able to get going on setting up cpython benchmark execution this week (no guarantee on the rate of progress though!). Cheers, -T On Thu, Aug 25, 2011 at 7:45 AM, Tennessee Leeuwenburg wrote: > Can do... I'll need a login. > > On 25/08/2011 4:51 AM, "Miquel Torres" wrote: >> hi Tennessee, >> >> as I am going to set up the Codespeed instance, you could try to >> configure the environment so that cpython benchmarks can be run (for >> the benchmarks pypy uses). Then we can configure the runner, and >> connect it to Codespeed. >> >> Miquel >> >> >> 2011/8/24 Jesse Noller : >>> I've given Miquel privileges to install the initial codespeed >>> deployment - the initial goals are really simple: >>> >>> 1> Deploy codespeed "as is" running pypy and cpython benchmarks[1] >>> 2> Work from there - show how CPython has evolved over time (just like >>> the pypy charts), etc. >>> >>> Modifying the benchmark suite/etc is out of scope for initial >>> deployment - the benchmarks as they sit today are an excellent jumping >>> off point. We can work on improvements from there. >>> >>> Miquel - is there a way Tennessee can help us get up and toddling? >>> >>> [1] http://speed.pypy.org/ >>> >>> >>> >>> On Wed, Aug 24, 2011 at 12:55 AM, Tennessee Leeuwenburg >>> wrote: >>>> Hi all, >>>> >>>> I'm more than happy to lend some effort here if the task is >>>> straightforward enough for a newcomer to PyPy to achieve. >>>> >>>> Cheers, >>>> -T >>>> >>>> On Sun, Aug 21, 2011 at 6:19 AM, Jesse Noller wrote: >>>>> The goal was to run the same thing that runs speed.PyPy for starters - >>>>> PyPy compared to CPython 2.x on the benchmarks would be a good start >>>>> >>>>> On Aug 20, 2011, at 4:16 PM, Miquel Torres >>>>> wrote: >>>>> >>>>>> Hi Jesse, >>>>>> >>>>>> setting up codespeed is no problem, but is there any kind of benchmark >>>>>> runner already? >>>>>> >>>>>> >>>>>> 2011/8/18 Jesse Noller : >>>>>>> I would like to see the speed machine see good use; has anyone freed >>>>>>> any time to setup codespeed or anything else we need to move forward? >>>>>>> _______________________________________________ >>>>>>> Speed mailing list >>>>>>> Speed at python.org >>>>>>> http://mail.python.org/mailman/listinfo/speed >>>>>>> >>>>> _______________________________________________ >>>>> Speed mailing list >>>>> Speed at python.org >>>>> http://mail.python.org/mailman/listinfo/speed >>>>> >>>> >>>> >>>> >>>> -- >>>> -------------------------------------------------- >>>> Tennessee Leeuwenburg >>>> http://myownhat.blogspot.com/ >>>> "Don't believe everything you think" >>>> >>> > -- -------------------------------------------------- Tennessee Leeuwenburg http://myownhat.blogspot.com/ "Don't believe everything you think" From jnoller at gmail.com Tue Aug 30 12:32:25 2011 From: jnoller at gmail.com (Jesse Noller) Date: Tue, 30 Aug 2011 06:32:25 -0400 Subject: [Speed] Pinging the group In-Reply-To: References:

Message-ID: I can add a shared user called "speedracer" On Aug 30, 2011, at 2:54 AM, Tennessee Leeuwenburg wrote: > Right... so I have my login working. I could do this in my own > username, but can I suggest a shared user for working in, to avoid any > dependencies on some particular person's account? I'm happy to create > a "worker" user for this purpose. > > Alternatively, is there some other way people would prefer to get things set up? > > I should be able to get going on setting up cpython benchmark > execution this week (no guarantee on the rate of progress though!). > > Cheers, > -T > > On Thu, Aug 25, 2011 at 7:45 AM, Tennessee Leeuwenburg > wrote: >> Can do... I'll need a login. >> >> On 25/08/2011 4:51 AM, "Miquel Torres" wrote: >>> hi Tennessee, >>> >>> as I am going to set up the Codespeed instance, you could try to >>> configure the environment so that cpython benchmarks can be run (for >>> the benchmarks pypy uses). Then we can configure the runner, and >>> connect it to Codespeed. >>> >>> Miquel >>> >>> >>> 2011/8/24 Jesse Noller : >>>> I've given Miquel privileges to install the initial codespeed >>>> deployment - the initial goals are really simple: >>>> >>>> 1> Deploy codespeed "as is" running pypy and cpython benchmarks[1] >>>> 2> Work from there - show how CPython has evolved over time (just like >>>> the pypy charts), etc. >>>> >>>> Modifying the benchmark suite/etc is out of scope for initial >>>> deployment - the benchmarks as they sit today are an excellent jumping >>>> off point. We can work on improvements from there. >>>> >>>> Miquel - is there a way Tennessee can help us get up and toddling? >>>> >>>> [1] http://speed.pypy.org/ >>>> >>>> >>>> >>>> On Wed, Aug 24, 2011 at 12:55 AM, Tennessee Leeuwenburg >>>> wrote: >>>>> Hi all, >>>>> >>>>> I'm more than happy to lend some effort here if the task is >>>>> straightforward enough for a newcomer to PyPy to achieve. >>>>> >>>>> Cheers, >>>>> -T >>>>> >>>>> On Sun, Aug 21, 2011 at 6:19 AM, Jesse Noller wrote: >>>>>> The goal was to run the same thing that runs speed.PyPy for starters - >>>>>> PyPy compared to CPython 2.x on the benchmarks would be a good start >>>>>> >>>>>> On Aug 20, 2011, at 4:16 PM, Miquel Torres >>>>>> wrote: >>>>>> >>>>>>> Hi Jesse, >>>>>>> >>>>>>> setting up codespeed is no problem, but is there any kind of benchmark >>>>>>> runner already? >>>>>>> >>>>>>> >>>>>>> 2011/8/18 Jesse Noller : >>>>>>>> I would like to see the speed machine see good use; has anyone freed >>>>>>>> any time to setup codespeed or anything else we need to move forward? >>>>>>>> _______________________________________________ >>>>>>>> Speed mailing list >>>>>>>> Speed at python.org >>>>>>>> http://mail.python.org/mailman/listinfo/speed >>>>>>>> >>>>>> _______________________________________________ >>>>>> Speed mailing list >>>>>> Speed at python.org >>>>>> http://mail.python.org/mailman/listinfo/speed >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> -------------------------------------------------- >>>>> Tennessee Leeuwenburg >>>>> http://myownhat.blogspot.com/ >>>>> "Don't believe everything you think" >>>>> >>>> >> > > > > -- > -------------------------------------------------- > Tennessee Leeuwenburg > http://myownhat.blogspot.com/ > "Don't believe everything you think" From jnoller at gmail.com Wed Aug 31 02:22:41 2011 From: jnoller at gmail.com (Jesse Noller) Date: Tue, 30 Aug 2011 20:22:41 -0400 Subject: [Speed] Moving the project forward Message-ID: Here's a summary (nicely put together by Nick Coghlan): - OSU/OSL have set up the machine itself (details in the July list archives) - I am the machine admin (I have root) - Tennessee and Miquel are working on getting codespeed up and running - I and Maciej are already too busy to handle the coordination/admin side of things I just added the "speedracer" account - a common account to setup things as needed. Currently, I don't see activity from Miquel on setting up the codespeed instance. I know Tennessee has been looking at setting up the runner. What we need is this, very simply: 1 - A working, running codespeed instance installed 2 - Benchmark runner(s) setup and going - for PyPy and CPython 2.x since the benchmarks don't run on Python 3 yet. Other needs/notes: - a project issue tracker doesn't appear to exist yet (needs to be done) - a better 'placeholder/about' page would be useful that offered links to: - the speed at python.org mailing list signup page - the issue tracker (once it exists) - the codespeed repo Ideally, the front landing page would end up looking like: http://speed.pypy.org/ - the aim is to eventually have the web front end running on different (but still OSU/OSL hosted) hardware, although that likely isn't critical right now - the current 5 GB /tmp size may be a problem for PyPy Where do we go from here - I can not be the one to keep pestering the group to make forward progress. On behalf of the PSF, and the CPython and PyPy teams, I got us a donated platform for running these shared, common benchmarks. Right now we have a 10,000$+ paper weight taking rack space in OSU/OSL. I need someone to take lead on this and get the project moving forward - as a reminder, here was the original proposal I made to the board, after PyCon 2011: """ Coming out of the PyCon VM and language summits, it was commonly agreed that PyPy, CPython, IronPython and Jython should strive to move to a common set of benchmarks and a single performance-oriented site. This was agreed upon by the maintainers present at the conference, and included leads from all of the major implementations. This project would be lead by the various VM development teams, and based around the Unladen Swallow/PyPy benchmark suite. The site would be derived from: http://speed.pypy.org/ There are already GSOC students potentially lined up to work on porting the test suite to Python 3! There, of course, is the requirement that we have: 1> A machine 2> Hosting for that machine And I took the job of finding both. As the OSU/OSL [1] has come up several times in discussions about free, monitored hosting, I felt that now would be the time to float the trial balloon and start a continuing relationship with the OSU/OSL team. I got to speak with some of the team at PyCon, and I was quite impressed with their enthusiasm and willingness to help out. """ I need help from everyone to get this up and running: the PyPy team is most familiar with the speed.pypy.org/codespeed system. If we could get a dump of what needs to be done to get things setup, that may help get more hands involved. I am feeling personally responsible that this has not been moving forward - I need your help to get this up and running for the betterment of CPython and PyPy. This project benefits both projects, and Python in general immensely. Once up and running, this system will be prominently placed on the Python.org home page, and be used by potential users to help select and evaluate their Python runtime. Jesse From jnoller at gmail.com Wed Aug 31 02:28:03 2011 From: jnoller at gmail.com (Jesse Noller) Date: Tue, 30 Aug 2011 20:28:03 -0400 Subject: [Speed] Moving the project forward In-Reply-To: References: Message-ID: (Re-sending intentionally - I wasn't subbed to pypy-dev and got rejected) On Tue, Aug 30, 2011 at 8:22 PM, Jesse Noller wrote: > Here's a summary (nicely put together by Nick Coghlan): > > - OSU/OSL have set up the machine itself (details in the July list archives) > - I am the machine admin (I have root) > - Tennessee and Miquel are working on getting codespeed up and running > > - I and Maciej are already too busy to handle the coordination/admin > side of things > > I just added the "speedracer" account - a common account to setup > things as needed. Currently, I don't see activity from Miquel on > setting up the codespeed instance. I know Tennessee has been looking > at setting up the runner. > > What we need is this, very simply: > > 1 - A working, running codespeed instance installed > 2 - Benchmark runner(s) setup and going - for PyPy and CPython 2.x > since the benchmarks don't run on Python 3 yet. > > > Other needs/notes: > - a project issue tracker doesn't appear to exist yet (needs to be done) > - a better 'placeholder/about' page would be useful that offered links to: > ?- the speed at python.org mailing list signup page > ?- the issue tracker (once it exists) > ?- the codespeed repo > > Ideally, the front landing page would end up looking like: > http://speed.pypy.org/ > > - the aim is to eventually have the web front end running on different > (but still OSU/OSL hosted) hardware, although that likely isn't > critical right now > > - the current 5 GB /tmp size may be a problem for PyPy > > Where do we go from here - I can not be the one to keep pestering the > group to make forward progress. On behalf of the PSF, and the CPython > and PyPy teams, I got us a donated platform for running these shared, > common benchmarks. Right now we have a 10,000$+ paper weight taking > rack space in OSU/OSL. > > I need someone to take lead on this and get the project moving forward > - as a reminder, here was the original proposal I made to the board, > after PyCon 2011: > > """ > Coming out of the PyCon VM and language summits, it was commonly > agreed that PyPy, CPython, IronPython and Jython should strive to move > to a common set of benchmarks and a single performance-oriented site. > This was agreed upon by the maintainers present at the conference, and > included leads from all of the major implementations. This project > would be lead by the various VM development teams, and based around > the Unladen Swallow/PyPy benchmark suite. The site would be derived > from: > > http://speed.pypy.org/ > > There are already GSOC students potentially lined up to work on > porting the test suite to Python 3! > > There, of course, is the requirement that we have: > > 1> A machine > 2> Hosting for that machine > > And I took the job of finding both. As the OSU/OSL [1] has come up > several times in discussions about free, monitored hosting, I felt > that now would be the time to float the trial balloon and start a > continuing relationship with the OSU/OSL team. I got to speak with > some of the team at PyCon, and I was quite impressed with their > enthusiasm and willingness to help out. > """ > > I need help from everyone to get this up and running: the PyPy team is > most familiar with the speed.pypy.org/codespeed system. If we could > get a dump of what needs to be done to get things setup, that may help > get more hands involved. > > I am feeling personally responsible that this has not been moving > forward - I need your help to get this up and running for the > betterment of CPython and PyPy. This project benefits both projects, > and Python in general immensely. > > Once up and running, this system will be prominently placed on the > Python.org home page, and be used by potential users to help select > and evaluate their Python runtime. > > Jesse > From alex.gaynor at gmail.com Wed Aug 31 02:35:13 2011 From: alex.gaynor at gmail.com (Alex Gaynor) Date: Tue, 30 Aug 2011 20:35:13 -0400 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References: Message-ID: I've gotten Noah Kantrowitz on here, he's doing some other infrastructure stuff for the PSF, and would like to include speed.python.org in the proper organization of the machines, rather than ad-hoc "everyone installs what they think it needs" :) Alex On Tue, Aug 30, 2011 at 8:28 PM, Jesse Noller wrote: > (Re-sending intentionally - I wasn't subbed to pypy-dev and got rejected) > > On Tue, Aug 30, 2011 at 8:22 PM, Jesse Noller wrote: > > Here's a summary (nicely put together by Nick Coghlan): > > > > - OSU/OSL have set up the machine itself (details in the July list > archives) > > - I am the machine admin (I have root) > > - Tennessee and Miquel are working on getting codespeed up and running > > > > - I and Maciej are already too busy to handle the coordination/admin > > side of things > > > > I just added the "speedracer" account - a common account to setup > > things as needed. Currently, I don't see activity from Miquel on > > setting up the codespeed instance. I know Tennessee has been looking > > at setting up the runner. > > > > What we need is this, very simply: > > > > 1 - A working, running codespeed instance installed > > 2 - Benchmark runner(s) setup and going - for PyPy and CPython 2.x > > since the benchmarks don't run on Python 3 yet. > > > > > > Other needs/notes: > > - a project issue tracker doesn't appear to exist yet (needs to be done) > > - a better 'placeholder/about' page would be useful that offered links > to: > > - the speed at python.org mailing list signup page > > - the issue tracker (once it exists) > > - the codespeed repo > > > > Ideally, the front landing page would end up looking like: > > http://speed.pypy.org/ > > > > - the aim is to eventually have the web front end running on different > > (but still OSU/OSL hosted) hardware, although that likely isn't > > critical right now > > > > - the current 5 GB /tmp size may be a problem for PyPy > > > > Where do we go from here - I can not be the one to keep pestering the > > group to make forward progress. On behalf of the PSF, and the CPython > > and PyPy teams, I got us a donated platform for running these shared, > > common benchmarks. Right now we have a 10,000$+ paper weight taking > > rack space in OSU/OSL. > > > > I need someone to take lead on this and get the project moving forward > > - as a reminder, here was the original proposal I made to the board, > > after PyCon 2011: > > > > """ > > Coming out of the PyCon VM and language summits, it was commonly > > agreed that PyPy, CPython, IronPython and Jython should strive to move > > to a common set of benchmarks and a single performance-oriented site. > > This was agreed upon by the maintainers present at the conference, and > > included leads from all of the major implementations. This project > > would be lead by the various VM development teams, and based around > > the Unladen Swallow/PyPy benchmark suite. The site would be derived > > from: > > > > http://speed.pypy.org/ > > > > There are already GSOC students potentially lined up to work on > > porting the test suite to Python 3! > > > > There, of course, is the requirement that we have: > > > > 1> A machine > > 2> Hosting for that machine > > > > And I took the job of finding both. As the OSU/OSL [1] has come up > > several times in discussions about free, monitored hosting, I felt > > that now would be the time to float the trial balloon and start a > > continuing relationship with the OSU/OSL team. I got to speak with > > some of the team at PyCon, and I was quite impressed with their > > enthusiasm and willingness to help out. > > """ > > > > I need help from everyone to get this up and running: the PyPy team is > > most familiar with the speed.pypy.org/codespeed system. If we could > > get a dump of what needs to be done to get things setup, that may help > > get more hands involved. > > > > I am feeling personally responsible that this has not been moving > > forward - I need your help to get this up and running for the > > betterment of CPython and PyPy. This project benefits both projects, > > and Python in general immensely. > > > > Once up and running, this system will be prominently placed on the > > Python.org home page, and be used by potential users to help select > > and evaluate their Python runtime. > > > > Jesse > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > http://mail.python.org/mailman/listinfo/pypy-dev > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero -------------- next part -------------- An HTML attachment was scrubbed... URL: From jnoller at gmail.com Wed Aug 31 02:37:05 2011 From: jnoller at gmail.com (Jesse Noller) Date: Tue, 30 Aug 2011 20:37:05 -0400 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References: Message-ID: Yes, I should have looped Noah in sooner. I have all the keys / passwords. Right now we need: 1. codespeed 2. benchmark runners I've installed a very basic system with Django, apache, mod_wsgi On Tue, Aug 30, 2011 at 8:35 PM, Alex Gaynor wrote: > I've gotten Noah Kantrowitz on here, he's doing some other infrastructure > stuff for the PSF, and would like to include speed.python.org in the proper > organization of the machines, rather than ad-hoc "everyone installs what > they think it needs" :) > Alex > > On Tue, Aug 30, 2011 at 8:28 PM, Jesse Noller wrote: >> >> (Re-sending intentionally - I wasn't subbed to pypy-dev and got rejected) >> >> On Tue, Aug 30, 2011 at 8:22 PM, Jesse Noller wrote: >> > Here's a summary (nicely put together by Nick Coghlan): >> > >> > - OSU/OSL have set up the machine itself (details in the July list >> > archives) >> > - I am the machine admin (I have root) >> > - Tennessee and Miquel are working on getting codespeed up and running >> > >> > - I and Maciej are already too busy to handle the coordination/admin >> > side of things >> > >> > I just added the "speedracer" account - a common account to setup >> > things as needed. Currently, I don't see activity from Miquel on >> > setting up the codespeed instance. I know Tennessee has been looking >> > at setting up the runner. >> > >> > What we need is this, very simply: >> > >> > 1 - A working, running codespeed instance installed >> > 2 - Benchmark runner(s) setup and going - for PyPy and CPython 2.x >> > since the benchmarks don't run on Python 3 yet. >> > >> > >> > Other needs/notes: >> > - a project issue tracker doesn't appear to exist yet (needs to be done) >> > - a better 'placeholder/about' page would be useful that offered links >> > to: >> > ?- the speed at python.org mailing list signup page >> > ?- the issue tracker (once it exists) >> > ?- the codespeed repo >> > >> > Ideally, the front landing page would end up looking like: >> > http://speed.pypy.org/ >> > >> > - the aim is to eventually have the web front end running on different >> > (but still OSU/OSL hosted) hardware, although that likely isn't >> > critical right now >> > >> > - the current 5 GB /tmp size may be a problem for PyPy >> > >> > Where do we go from here - I can not be the one to keep pestering the >> > group to make forward progress. On behalf of the PSF, and the CPython >> > and PyPy teams, I got us a donated platform for running these shared, >> > common benchmarks. Right now we have a 10,000$+ paper weight taking >> > rack space in OSU/OSL. >> > >> > I need someone to take lead on this and get the project moving forward >> > - as a reminder, here was the original proposal I made to the board, >> > after PyCon 2011: >> > >> > """ >> > Coming out of the PyCon VM and language summits, it was commonly >> > agreed that PyPy, CPython, IronPython and Jython should strive to move >> > to a common set of benchmarks and a single performance-oriented site. >> > This was agreed upon by the maintainers present at the conference, and >> > included leads from all of the major implementations. This project >> > would be lead by the various VM development teams, and based around >> > the Unladen Swallow/PyPy benchmark suite. The site would be derived >> > from: >> > >> > http://speed.pypy.org/ >> > >> > There are already GSOC students potentially lined up to work on >> > porting the test suite to Python 3! >> > >> > There, of course, is the requirement that we have: >> > >> > 1> A machine >> > 2> Hosting for that machine >> > >> > And I took the job of finding both. As the OSU/OSL [1] has come up >> > several times in discussions about free, monitored hosting, I felt >> > that now would be the time to float the trial balloon and start a >> > continuing relationship with the OSU/OSL team. I got to speak with >> > some of the team at PyCon, and I was quite impressed with their >> > enthusiasm and willingness to help out. >> > """ >> > >> > I need help from everyone to get this up and running: the PyPy team is >> > most familiar with the speed.pypy.org/codespeed system. If we could >> > get a dump of what needs to be done to get things setup, that may help >> > get more hands involved. >> > >> > I am feeling personally responsible that this has not been moving >> > forward - I need your help to get this up and running for the >> > betterment of CPython and PyPy. This project benefits both projects, >> > and Python in general immensely. >> > >> > Once up and running, this system will be prominently placed on the >> > Python.org home page, and be used by potential users to help select >> > and evaluate their Python runtime. >> > >> > Jesse >> > >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> http://mail.python.org/mailman/listinfo/pypy-dev > > > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." -- Evelyn Beatrice Hall (summarizing Voltaire) > "The people's good is the highest law." -- Cicero > > From noah at coderanger.net Wed Aug 31 02:37:52 2011 From: noah at coderanger.net (Noah Kantrowitz) Date: Tue, 30 Aug 2011 17:37:52 -0700 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References: Message-ID: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> 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). --Noah On Aug 30, 2011, at 5:35 PM, Alex Gaynor wrote: > I've gotten Noah Kantrowitz on here, he's doing some other infrastructure stuff for the PSF, and would like to include speed.python.org in the proper organization of the machines, rather than ad-hoc "everyone installs what they think it needs" :) > > Alex > > On Tue, Aug 30, 2011 at 8:28 PM, Jesse Noller wrote: > (Re-sending intentionally - I wasn't subbed to pypy-dev and got rejected) > > On Tue, Aug 30, 2011 at 8:22 PM, Jesse Noller wrote: > > Here's a summary (nicely put together by Nick Coghlan): > > > > - OSU/OSL have set up the machine itself (details in the July list archives) > > - I am the machine admin (I have root) > > - Tennessee and Miquel are working on getting codespeed up and running > > > > - I and Maciej are already too busy to handle the coordination/admin > > side of things > > > > I just added the "speedracer" account - a common account to setup > > things as needed. Currently, I don't see activity from Miquel on > > setting up the codespeed instance. I know Tennessee has been looking > > at setting up the runner. > > > > What we need is this, very simply: > > > > 1 - A working, running codespeed instance installed > > 2 - Benchmark runner(s) setup and going - for PyPy and CPython 2.x > > since the benchmarks don't run on Python 3 yet. > > > > > > Other needs/notes: > > - a project issue tracker doesn't appear to exist yet (needs to be done) > > - a better 'placeholder/about' page would be useful that offered links to: > > - the speed at python.org mailing list signup page > > - the issue tracker (once it exists) > > - the codespeed repo > > > > Ideally, the front landing page would end up looking like: > > http://speed.pypy.org/ > > > > - the aim is to eventually have the web front end running on different > > (but still OSU/OSL hosted) hardware, although that likely isn't > > critical right now > > > > - the current 5 GB /tmp size may be a problem for PyPy > > > > Where do we go from here - I can not be the one to keep pestering the > > group to make forward progress. On behalf of the PSF, and the CPython > > and PyPy teams, I got us a donated platform for running these shared, > > common benchmarks. Right now we have a 10,000$+ paper weight taking > > rack space in OSU/OSL. > > > > I need someone to take lead on this and get the project moving forward > > - as a reminder, here was the original proposal I made to the board, > > after PyCon 2011: > > > > """ > > Coming out of the PyCon VM and language summits, it was commonly > > agreed that PyPy, CPython, IronPython and Jython should strive to move > > to a common set of benchmarks and a single performance-oriented site. > > This was agreed upon by the maintainers present at the conference, and > > included leads from all of the major implementations. This project > > would be lead by the various VM development teams, and based around > > the Unladen Swallow/PyPy benchmark suite. The site would be derived > > from: > > > > http://speed.pypy.org/ > > > > There are already GSOC students potentially lined up to work on > > porting the test suite to Python 3! > > > > There, of course, is the requirement that we have: > > > > 1> A machine > > 2> Hosting for that machine > > > > And I took the job of finding both. As the OSU/OSL [1] has come up > > several times in discussions about free, monitored hosting, I felt > > that now would be the time to float the trial balloon and start a > > continuing relationship with the OSU/OSL team. I got to speak with > > some of the team at PyCon, and I was quite impressed with their > > enthusiasm and willingness to help out. > > """ > > > > I need help from everyone to get this up and running: the PyPy team is > > most familiar with the speed.pypy.org/codespeed system. If we could > > get a dump of what needs to be done to get things setup, that may help > > get more hands involved. > > > > I am feeling personally responsible that this has not been moving > > forward - I need your help to get this up and running for the > > betterment of CPython and PyPy. This project benefits both projects, > > and Python in general immensely. > > > > Once up and running, this system will be prominently placed on the > > Python.org home page, and be used by potential users to help select > > and evaluate their Python runtime. > > > > Jesse > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > http://mail.python.org/mailman/listinfo/pypy-dev > > > > -- > "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) > "The people's good is the highest law." -- Cicero > > _______________________________________________ > Speed mailing list > Speed at python.org > http://mail.python.org/mailman/listinfo/speed -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4789 bytes Desc: not available URL: From noah at coderanger.net Wed Aug 31 02:47:20 2011 From: noah at coderanger.net (Noah Kantrowitz) Date: Tue, 30 Aug 2011 17:47:20 -0700 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References:

Message-ID: <3A1ED2E3-2B75-4763-8A36-55011493245D@coderanger.net> Is there an a readme for installing those somewhere? If someone can show me the commands a human would run I can handle scripting them :-) --Noah On Aug 30, 2011, at 5:37 PM, Jesse Noller wrote: > Yes, I should have looped Noah in sooner. > > I have all the keys / passwords. Right now we need: > > 1. codespeed > 2. benchmark runners > > I've installed a very basic system with Django, apache, mod_wsgi > > On Tue, Aug 30, 2011 at 8:35 PM, Alex Gaynor wrote: >> I've gotten Noah Kantrowitz on here, he's doing some other infrastructure >> stuff for the PSF, and would like to include speed.python.org in the proper >> organization of the machines, rather than ad-hoc "everyone installs what >> they think it needs" :) >> Alex >> >> On Tue, Aug 30, 2011 at 8:28 PM, Jesse Noller wrote: >>> >>> (Re-sending intentionally - I wasn't subbed to pypy-dev and got rejected) >>> >>> On Tue, Aug 30, 2011 at 8:22 PM, Jesse Noller wrote: >>>> Here's a summary (nicely put together by Nick Coghlan): >>>> >>>> - OSU/OSL have set up the machine itself (details in the July list >>>> archives) >>>> - I am the machine admin (I have root) >>>> - Tennessee and Miquel are working on getting codespeed up and running >>>> >>>> - I and Maciej are already too busy to handle the coordination/admin >>>> side of things >>>> >>>> I just added the "speedracer" account - a common account to setup >>>> things as needed. Currently, I don't see activity from Miquel on >>>> setting up the codespeed instance. I know Tennessee has been looking >>>> at setting up the runner. >>>> >>>> What we need is this, very simply: >>>> >>>> 1 - A working, running codespeed instance installed >>>> 2 - Benchmark runner(s) setup and going - for PyPy and CPython 2.x >>>> since the benchmarks don't run on Python 3 yet. >>>> >>>> >>>> Other needs/notes: >>>> - a project issue tracker doesn't appear to exist yet (needs to be done) >>>> - a better 'placeholder/about' page would be useful that offered links >>>> to: >>>> - the speed at python.org mailing list signup page >>>> - the issue tracker (once it exists) >>>> - the codespeed repo >>>> >>>> Ideally, the front landing page would end up looking like: >>>> http://speed.pypy.org/ >>>> >>>> - the aim is to eventually have the web front end running on different >>>> (but still OSU/OSL hosted) hardware, although that likely isn't >>>> critical right now >>>> >>>> - the current 5 GB /tmp size may be a problem for PyPy >>>> >>>> Where do we go from here - I can not be the one to keep pestering the >>>> group to make forward progress. On behalf of the PSF, and the CPython >>>> and PyPy teams, I got us a donated platform for running these shared, >>>> common benchmarks. Right now we have a 10,000$+ paper weight taking >>>> rack space in OSU/OSL. >>>> >>>> I need someone to take lead on this and get the project moving forward >>>> - as a reminder, here was the original proposal I made to the board, >>>> after PyCon 2011: >>>> >>>> """ >>>> Coming out of the PyCon VM and language summits, it was commonly >>>> agreed that PyPy, CPython, IronPython and Jython should strive to move >>>> to a common set of benchmarks and a single performance-oriented site. >>>> This was agreed upon by the maintainers present at the conference, and >>>> included leads from all of the major implementations. This project >>>> would be lead by the various VM development teams, and based around >>>> the Unladen Swallow/PyPy benchmark suite. The site would be derived >>>> from: >>>> >>>> http://speed.pypy.org/ >>>> >>>> There are already GSOC students potentially lined up to work on >>>> porting the test suite to Python 3! >>>> >>>> There, of course, is the requirement that we have: >>>> >>>> 1> A machine >>>> 2> Hosting for that machine >>>> >>>> And I took the job of finding both. As the OSU/OSL [1] has come up >>>> several times in discussions about free, monitored hosting, I felt >>>> that now would be the time to float the trial balloon and start a >>>> continuing relationship with the OSU/OSL team. I got to speak with >>>> some of the team at PyCon, and I was quite impressed with their >>>> enthusiasm and willingness to help out. >>>> """ >>>> >>>> I need help from everyone to get this up and running: the PyPy team is >>>> most familiar with the speed.pypy.org/codespeed system. If we could >>>> get a dump of what needs to be done to get things setup, that may help >>>> get more hands involved. >>>> >>>> I am feeling personally responsible that this has not been moving >>>> forward - I need your help to get this up and running for the >>>> betterment of CPython and PyPy. This project benefits both projects, >>>> and Python in general immensely. >>>> >>>> Once up and running, this system will be prominently placed on the >>>> Python.org home page, and be used by potential users to help select >>>> and evaluate their Python runtime. >>>> >>>> Jesse >>>> >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev at python.org >>> http://mail.python.org/mailman/listinfo/pypy-dev >> >> >> >> -- >> "I disapprove of what you say, but I will defend to the death your right to >> say it." -- Evelyn Beatrice Hall (summarizing Voltaire) >> "The people's good is the highest law." -- Cicero >> >> > _______________________________________________ > Speed mailing list > Speed at python.org > http://mail.python.org/mailman/listinfo/speed -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4789 bytes Desc: not available URL: From anto.cuni at gmail.com Wed Aug 31 10:12:45 2011 From: anto.cuni at gmail.com (Antonio Cuni) Date: Wed, 31 Aug 2011 10:12:45 +0200 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References:

Message-ID: <4E5DECFD.7020203@gmail.com> Hi Jesse, hi all, On 31/08/11 02:37, Jesse Noller wrote: > Yes, I should have looped Noah in sooner. > > I have all the keys / passwords. Right now we need: > > 1. codespeed > 2. benchmark runners The second item is divided into two sub-items: the runner itself, and something that triggers a run nightly/on request. In PyPy, we currently use a modified version of the Unladen Swallow benchmark runner (look at runner.py): https://bitbucket.org/pypy/benchmarks/src in its current state, it is sub-optimal, because it was designed to compare two pythons side-by-side, and not to save the results and then upload them to a website. As a consequence, it always runs the benchmarks twice. With PyPy, it's lesser of a problem because for each binary we always run the benchmarks with the default options and with "--jit off" anyway, but for CPython running them twice would result in a waste of time. I suppose that the current runner is good enough for now and to get started, however at some point it will need some care. Then, we need something which triggers the actual benchmark run. In PyPy, we use buildbot, and each benchmark run first do a full translation, then executes the benchmarks. 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. ciao, Anto From anto.cuni at gmail.com Wed Aug 31 10:19:10 2011 From: anto.cuni at gmail.com (Antonio Cuni) Date: Wed, 31 Aug 2011 10:19:10 +0200 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: <4E5DECFD.7020203@gmail.com> References:

<4E5DECFD.7020203@gmail.com> Message-ID: <4E5DEE7E.3080801@gmail.com> 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 From jnoller at gmail.com Wed Aug 31 11:52:39 2011 From: jnoller at gmail.com (Jesse Noller) Date: Wed, 31 Aug 2011 05:52:39 -0400 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: <20110831074312.GJ99611@nexus.in-nomine.org> References: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> <20110831074312.GJ99611@nexus.in-nomine.org> Message-ID: Noah is one person, yes you should help On Aug 31, 2011, at 3:43 AM, Jeroen Ruigrok van der Werven wrote: > -On [20110831 02:57], Noah Kantrowitz (noah at 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 > ????? ?????? ??? ?? ?????? > http://www.in-nomine.org/ | GPG: 2EAC625B > Under this standard shalt thou conquer... From ncoghlan at gmail.com Wed Aug 31 12:22:31 2011 From: ncoghlan at gmail.com (Nick Coghlan) Date: Wed, 31 Aug 2011 20:22:31 +1000 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> <20110831074312.GJ99611@nexus.in-nomine.org> Message-ID: On Wed, Aug 31, 2011 at 7:52 PM, Jesse Noller wrote: > Noah is one person, yes you should help > > On Aug 31, 2011, at 3:43 AM, Jeroen Ruigrok van der Werven wrote: > >> -On [20110831 02:57], Noah Kantrowitz (noah at 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? Backing Jesse up on this one: it's generally nice to have at least two people able to do things so that one person going on holidays (or whatever) doesn't prevent progress. speed.python.org is really going to need its own supporting community to fulfil its potential, and the existing CPython and PyPy devs already have pretty full plates, so relying on us to make it happen won't work so well. Getting started is going to be a little rocky, since decision making responsibilities aren't at all clear and there will need to be a bit of "self-appointment" involved. So I'll ask a (deceptively) simple question: who's going to set up a BitBucket project to use as the issue tracker for speed.python.org (at least initially), populate it with information about the current plans for the speed.python.org site and then announce that to this list? Whoever does this will be volunteering themselves for a bit of work in helping to coordinate things, especially in granting other people access to the project and turning the summary in Jesse's email into a list of initial tasks, but they'll also be playing a key part in helping to build a useful community resource. But the field's wide open as to who that person will be - all it really takes at this point is a BitBucket account and a willingness to say "I can do this!" :) Cheers, Nick. -- Nick Coghlan?? |?? ncoghlan at gmail.com?? |?? Brisbane, Australia From asmodai at in-nomine.org Wed Aug 31 13:01:37 2011 From: asmodai at in-nomine.org (Jeroen Ruigrok van der Werven) Date: Wed, 31 Aug 2011 13:01:37 +0200 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> <20110831074312.GJ99611@nexus.in-nomine.org>

Message-ID: <20110831110137.GK99611@nexus.in-nomine.org> -On [20110831 12:22], Nick Coghlan (ncoghlan at gmail.com) wrote: >So I'll ask a (deceptively) simple question: who's going to set up a >BitBucket project to use as the issue tracker for speed.python.org (at >least initially), populate it with information about the current plans >for the speed.python.org site and then announce that to this list? Something like: https://bitbucket.org/asmodai/python-speed/issues?status=new&status=open ? -- Jeroen Ruigrok van der Werven / asmodai ????? ?????? ??? ?? ?????? http://www.in-nomine.org/ | GPG: 2EAC625B Take thy beak from out my heart and take thy form from off my door! From ncoghlan at gmail.com Wed Aug 31 13:28:14 2011 From: ncoghlan at gmail.com (Nick Coghlan) Date: Wed, 31 Aug 2011 21:28:14 +1000 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: <20110831110137.GK99611@nexus.in-nomine.org> References: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> <20110831074312.GJ99611@nexus.in-nomine.org>

<20110831110137.GK99611@nexus.in-nomine.org> Message-ID: On Wed, Aug 31, 2011 at 9:01 PM, Jeroen Ruigrok van der Werven wrote: > -On [20110831 12:22], Nick Coghlan (ncoghlan at gmail.com) wrote: >>So I'll ask a (deceptively) simple question: who's going to set up a >>BitBucket project to use as the issue tracker for speed.python.org (at >>least initially), populate it with information about the current plans >>for the speed.python.org site and then announce that to this list? > > Something like: > > https://bitbucket.org/asmodai/python-speed/issues?status=new&status=open > > ? Indeed :) Hopefully those already (or just interested in) working on some of those items will be happy with the BitBucket option for coordination, so you can start adding more contributors... Cheers, Nick. -- Nick Coghlan?? |?? ncoghlan at gmail.com?? |?? Brisbane, Australia From lac at openend.se Wed Aug 31 13:33:08 2011 From: lac at openend.se (Laura Creighton) Date: Wed, 31 Aug 2011 13:33:08 +0200 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: Message from Nick Coghlan of "Wed, 31 Aug 2011 21:28:14 +1000." References: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> <20110831074312.GJ99611@nexus.in-nomine.org>

<20110831110137.GK99611@nexus.in-nomine.org> Message-ID: <201108311133.p7VBX8ZB030432@theraft.openend.se> I want to know the status of DasIch's GSoC project to work on the coderunner. i.e. GSoC is over now, so we can start hacking on whereever he left off, correct? Laura From jnoller at gmail.com Wed Aug 31 13:39:31 2011 From: jnoller at gmail.com (Jesse Noller) Date: Wed, 31 Aug 2011 07:39:31 -0400 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: <201108311133.p7VBX8ZB030432@theraft.openend.se> References: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> <20110831074312.GJ99611@nexus.in-nomine.org>

<20110831110137.GK99611@nexus.in-nomine.org> <201108311133.p7VBX8ZB030432@theraft.openend.se> Message-ID: Afaik, yes On Aug 31, 2011, at 7:33 AM, Laura Creighton wrote: > I want to know the status of DasIch's GSoC project to work on the > coderunner. i.e. GSoC is over now, so we can start hacking on > whereever he left off, correct? > > Laura > _______________________________________________ > Speed mailing list > Speed at python.org > http://mail.python.org/mailman/listinfo/speed From jnoller at gmail.com Wed Aug 31 17:00:44 2011 From: jnoller at gmail.com (Jesse Noller) Date: Wed, 31 Aug 2011 11:00:44 -0400 Subject: [Speed] Moving the project forward In-Reply-To: References: Message-ID: I've put up a splash page for the project this AM: http://speed.python.org/ jesse From tobami at googlemail.com Wed Aug 31 20:34:49 2011 From: tobami at googlemail.com (Miquel Torres) Date: Wed, 31 Aug 2011 20:34:49 +0200 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References: Message-ID: 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 : > I've put up a splash page for the project this AM: > > http://speed.python.org/ > > jesse > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > http://mail.python.org/mailman/listinfo/pypy-dev > From noah at coderanger.net Wed Aug 31 22:06:45 2011 From: noah at coderanger.net (Noah Kantrowitz) Date: Wed, 31 Aug 2011 13:06:45 -0700 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References:

Message-ID: <6F0743E2-3C52-4463-B790-B995B02D4ED1@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 : >> I've put up a splash page for the project this AM: >> >> http://speed.python.org/ >> >> jesse >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> http://mail.python.org/mailman/listinfo/pypy-dev >> > _______________________________________________ > Speed mailing list > Speed at python.org > http://mail.python.org/mailman/listinfo/speed -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4789 bytes Desc: not available URL: From brett at python.org Wed Aug 31 22:11:51 2011 From: brett at python.org (Brett Cannon) Date: Wed, 31 Aug 2011 13:11:51 -0700 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References:

Message-ID: On Wed, Aug 31, 2011 at 11:34, 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. [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. From tobami at googlemail.com Wed Aug 31 22:12:58 2011 From: tobami at googlemail.com (Miquel Torres) Date: Wed, 31 Aug 2011 22:12:58 +0200 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: <6F0743E2-3C52-4463-B790-B995B02D4ED1@coderanger.net> References:

<6F0743E2-3C52-4463-B790-B995B02D4ED1@coderanger.net> Message-ID: 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 : > 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 : >>> I've put up a splash page for the project this AM: >>> >>> http://speed.python.org/ >>> >>> jesse >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev at python.org >>> http://mail.python.org/mailman/listinfo/pypy-dev >>> >> _______________________________________________ >> Speed mailing list >> Speed at python.org >> http://mail.python.org/mailman/listinfo/speed > > From noah at coderanger.net Wed Aug 31 22:28:22 2011 From: noah at coderanger.net (Noah Kantrowitz) Date: Wed, 31 Aug 2011 13:28:22 -0700 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: References:

<6F0743E2-3C52-4463-B790-B995B02D4ED1@coderanger.net> Message-ID: <7D8FD0F4-2107-4556-A8A8-139CFCA831AD@coderanger.net> Its all branches all the way down, so we can start work anywhere and push it to an "official" PSF bin later I think. I'm sure we will want to host a mirror of it on the python.org hg server too, just for discoverability. --Noah On Aug 31, 2011, at 1:12 PM, Miquel Torres wrote: > 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 : >> 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 : >>>> I've put up a splash page for the project this AM: >>>> >>>> http://speed.python.org/ >>>> >>>> jesse >>>> _______________________________________________ >>>> pypy-dev mailing list >>>> pypy-dev at python.org >>>> http://mail.python.org/mailman/listinfo/pypy-dev >>>> >>> _______________________________________________ >>> Speed mailing list >>> Speed at python.org >>> http://mail.python.org/mailman/listinfo/speed >> >> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4789 bytes Desc: not available URL: From asmodai at in-nomine.org Wed Aug 31 09:43:24 2011 From: asmodai at in-nomine.org (Jeroen Ruigrok van der Werven) Date: Wed, 31 Aug 2011 07:43:24 -0000 Subject: [Speed] [pypy-dev] Moving the project forward In-Reply-To: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> References: <32A28CE2-DA63-4B47-9938-1DDCE702168E@coderanger.net> Message-ID: <20110831074312.GJ99611@nexus.in-nomine.org> -On [20110831 02:57], Noah Kantrowitz (noah at 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 ????? ?????? ??? ?? ?????? http://www.in-nomine.org/ | GPG: 2EAC625B Under this standard shalt thou conquer...