Showing content from http://mail.python.org/pipermail/python-dev/attachments/20110330/ce1c8fa7/attachment.html below:
<div>Hi Nick, Jesse,</div><div><br></div>Thanks both for your responses, it's much appreciated! It's very useful to have a clear pointer to the right place to begin looking.<div><br></div><div>Regards,</div><div>-Tennessee<br>
<br><div class="gmail_quote">On Tue, Mar 29, 2011 at 10:47 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;">
<div><div></div><div class="h5">On Tue, Mar 29, 2011 at 7:00 AM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:<br>
> On Tue, Mar 29, 2011 at 8:01 PM, Tennessee Leeuwenburg<br>
> <<a href="mailto:tleeuwenburg@gmail.com">tleeuwenburg@gmail.com</a>> wrote:<br>
>> PyPy maintains <a href="http://speed.pypy.org/" target="_blank">http://speed.pypy.org/</a>, which provides very clear information<br>
>> about the relative performance of PyPy trunk against some version of cpython<br>
>> (presumably 2.6 or 2.7). I'm not aware of a similar site for cpython, but<br>
>> that could easily just be my ignorance speaking.<br>
>> My interest is that I'm looking at building a benchmarking solution at work.<br>
>> and I can't think of a better way to build something good and general than<br>
>> to try and write something that could potentially be released as open source<br>
>> and be useful to others. As such I thought that benchmarking cpython would<br>
>> be a great use case, but I want to find out as much as I can about how<br>
>> people currently go about benchmarking Python. Initially I'm just looking at<br>
>> CPU profiling since it's easiest.<br>
><br>
> One of the points coming out of the VM summit at Pycon is actually<br>
> that we want to create a shared benchmarking site for CPython, PyPy,<br>
> Jython, IronPython (and possibly Stackless) under the <a href="http://python.org" target="_blank">python.org</a><br>
> banner (either <a href="http://speed.python.org" target="_blank">speed.python.org</a>, or possibly <a href="http://performance.python.org" target="_blank">performance.python.org</a>,<br>
> since we want to do memory profiling as well).<br>
><br>
> <a href="http://speed.pypy.org" target="_blank">speed.pypy.org</a> will be the reference site for this, but Maciej<br>
> indicated at the VM summit that the code that runs that site needs<br>
> some improvements before it will really be up to the task of<br>
> effectively benchmarking multiple targets.<br>
><br>
> So, according to <a href="http://speed.pypy.org/about/" target="_blank">http://speed.pypy.org/about/</a>, the place to start with<br>
> your benchmarking system would probably be<br>
> <a href="https://github.com/tobami/codespeed" target="_blank">https://github.com/tobami/codespeed</a>.<br>
><br>
> Cheers,<br>
> Nick.<br>
<br>
</div></div>Essentially echoing what nick said. I'm currently working on getting<br>
the HW for this together.<br>
</blockquote></div><br><br clear="all"><br>-- <br>--------------------------------------------------<br>Tennessee Leeuwenburg<br><a href="http://myownhat.blogspot.com/">http://myownhat.blogspot.com/</a><br>"Don't believe everything you think"<br>
</div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4