[
https://issues.apache.org/jira/browse/AVRO-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017524#comment-13017524
]
Doug Cutting commented on AVRO-800:
-----------------------------------
My hack above is really fragile. If someone adds a new test in the middle of
Perf.java or otherwise changes its output then the graph will break. It would
be better to move some of the logic into Perf.java. It might produce a file
named <date>.json containing a record for each test run, e.g.:
{code}
{"name": "ReadInt", "mbps":357}
{"name": "WriteInt", "mbps":298}
{code}
Then we could write something that takes a directory of these files and
produces the TSV file to plot, e.g.:
{code}
Date ReadInt WriteInt
20110414 357 298
...
{code}
This would leave blanks in columns where some files contain a test that others
do not. It could also invoke gnuplot to produce the .png image from the TSV
file.
> plot performance over time
> --------------------------
>
> Key: AVRO-800
> URL: https://issues.apache.org/jira/browse/AVRO-800
> Project: Avro
> Issue Type: New Feature
> Reporter: Doug Cutting
> Attachments: avro-perf.tar.gz, avro-perf.tar.gz, perf.png, perf.png
>
>
> It might be useful to have a nightly repository of Avro performance
> statistics, so that we can plot performance changes over time.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
