[pypy-dev] speed.pypy.org quick update
tobami at googlemail.com
Sun Mar 14 19:06:42 CET 2010
- About showing axis labels, it can be done, of course, as they are for a
single timeline plot. But please bear in mind that the timeline grid is a
bit of a compromise UI-wise. It currently shows 20 plots (!) at the same
time (probably more in the future if Maciej keeps adding more). Showing a
"seconds" or "lower is better" in all of them would be a big waste of screen
real state. You also have to assume that people who access this site are
knowledgeable enough for being able to interpret plots correctly, specially
if the single plot view does specify units and ALL yaxis are in seconds. It
is not like they change to flops and then to mips and seconds again...
2010/3/14 Miquel Torres <tobami at googlemail.com>
> Hey, thanks for the feedback.
> - In the timeline grid, I agree showing coordinates is not useful. I have
> disabled that
> - The rounding: yes, it is pretty stupid to show "revision 71807.4". That
> goes away once coordinates are disabled though.
> >I think this is a clear way to show performance for non developers and is
> great even for developers, it is a win
> > win website :)
> I'm very glad to hear that. That was exactly my intention when starting the
> project :-D
> I had to scratch my itch of wanting to better follow pypy's performance as
> a common python developer, but I also recognized that being such a
> performance oriented project, pypy badly needed good performance regression
> monitoring and progress tracking.
> 2010/3/14 Leonardo Santagada <santagada at gmail.com>
>> On Mar 13, 2010, at 10:28 PM, Marius Gedminas wrote:
>> > On Fri, Mar 12, 2010 at 06:37:49PM -0300, Leonardo Santagada wrote:
>> >> On Mar 12, 2010, at 6:08 PM, Alex Gaynor wrote:
>> >>> So one tiny pony I have is that on the tablular timeline page
>> >>> (http://speed.pypy.org/timeline/) that when you mouseover a graph it
>> >>> doesn't show the "coordinates" on graphs of those sizes I don't think
>> >>> it adds any value, and it's farily distracting.
>> >> For a start it could be removed (that should be pretty easy)
>> > Actually, if you added units to those numbers, they could answer
>> > important questions like "is a higher line better or is a lower line
>> > better?"
>> Yes but axis should be named in a always visible place, so when people see
>> the graphs they know what they mean.
>> >> but as a
>> >> second step it would be interesting to highlight and maybe show the
>> >> revision or time of the closest point (if revision then highlight all
>> >> points of that revision).
>> > Some kind of rounding would be nice, as seeing "0.6 seconds in revision
>> > 71807.4" is a bit weird.
>> No rounding but actually showing the data for the closest point and not
>> where the mouse is over.
>> > Very shiny website, BTW, I love it.
>> I think this is a clear way to show performance for non developers and is
>> great even for developers, it is a win win website :)
>> Leonardo Santagada
>> santagada at gmail.com
>> pypy-dev at codespeak.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pypy-dev