[pypy-dev] Improving the pypy website (and benchmarks)

Miquel Torres tobami at googlemail.com
Tue Sep 22 15:58:46 CEST 2009

Hi Holger,

I'm glad if I can be of any help.

> I can imagine you could start immediately with helping in the
> benchmarking visualization area.
Fine. The first step would be to agree on how the benchmark data will be
saved (a text or xml format?. to the website's backend DB?) so that the test
suite is designed that way from the beginning. Is there a pypy wiki?, how do
you document the possibilities and final decisions on such matters?.

We also need to agree on how the process to improve the website should look
like (see, I'm a newcomer, I don't know how you go about things here :-)

> Do you by chance happen to be able to come to
> the prospective 6-13th November PyPy-Sprint in Duesseldorf?
I was planning to travel to Germany over the next few months, but in
November I don't know whether time nor funds will permit. I'll look into it,
it would surely be awesome!.



2009/9/22 holger krekel <holger at merlinux.eu>

> Hi Miquel,
> thanks for your mail and great offers!  I setup much of the current website
> infrastructure and agree there is lots of room for improvements and that it
> gets about time.  I can imagine you could start immediately with helping in
> the
> benchmarking visualization area.  Do you by chance happen to be able to
> come to
> the prospective 6-13th November PyPy-Sprint in Duesseldorf?
> cheers,
> holger
> On Mon, Sep 21, 2009 at 22:35 +0200, Miquel Torres wrote:
> > Hi, this is my first post on the pypy-dev mailing list. I've commented on
> > the pypy blog, and was encouraged by fijal to continue here.
> > My daily job involves some web coding (HTML, javascript, Django...),
> python
> > coding (frameworks, scipts), usability analysis, and opensource project
> > management among other tasks, so I have some ideas on how to improve
> pypy's
> > website, as well as the project's visibility. I find the pypy project
> > extremely interesting (and important!), and I think that once a version
> of
> > the JIT gets into a release the project will get a lot more attention.
> >
> > There are two things I want to discuss:
> >
> > One is improving pypy's main website. While the current site has served
> its
> > purpose, it is mostly a pypy developers site. Better structure and
> > navigation would be desirable when pypy becomes popular among mainstream
> > python developers. So there are two options: to keep the current
> > http://codespeak.net/pypy/dist/pypy/doc/index.html site for developers
> and
> > develop a new www.pypy.org site, or improve the current one.
> >
> > The tasks to perform would be:
> > - Agree on a new website or keeping and improving the current one
> > - Choose a CMS (or hand-code or whatever) to craft the website
> > - Define a navigation menu with key areas (about, download, news,
> > roadmap, benchmarks, developement...)
> > - Visual design
> > - Code ;.)
> >
> > I can help with some (or all) of these tasks.
> >
> > Another matter are benchmarks. Because it is the project's most visible
> > "feature" or "result", it would be great to publish a set of benchmarks
> so
> > that python users can keep track of performance across different versions
> > (cpython 2.6 vs pypy1.1, Jython, etc...). That way they can keep track of
> > performance improvements as well as decide when it becomes attractive for
> > them to make the switch from cpython. It would be the best advertisement
> for
> > the project. The best case would be if you internally perform performance
> > test to prevent performance regression on new releases, and that same
> data
> > could be also be automatically published on the web, in the dev pages
> > during development, and .in the "public" pages for final releases.
> >
> > So the tasks here would be:
> > - Define a set of standard benchmarks that will serve as performance
> tests
> > for every new release (including alphas and betas)
> > - Create a script that gathers all the data for developers to analyse and
> > spot performance regressions and bugs AND outputs the data in such a way
> > that it can be automatically published on the website (so no extra
> > maintenance workload)
> > - Code the web page that beautifully shows the data in a suitable format
> > (tables, graphs)
> >
> > I have recently done some work on dynamic javascript (or python)
> plotting,
> > so I can take care of the last part relatively easily. I could also help
> > with the second task.
> >
> > So I leave it there for you to discuss. What do you think of it all?
> >
> > Cheers,
> >
> > Miquel
> > _______________________________________________
> > pypy-dev at codespeak.net
> > http://codespeak.net/mailman/listinfo/pypy-dev
>  <http://merlinux.eu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20090922/8d56a332/attachment.html>

More information about the Pypy-dev mailing list