chapel-lang/chapel — pull request #302 by bradcray (2014-09-04 20:03:23+00:00)
Title: Update to graphs in performance tracking suite

It's been a long time since we considered which graphs are
in the performance graphing suite. Here, I did a refresh
on them for my performance triage week as follows:

* EP Stream -- I took the version that has --local and --no-local results
though I think all our stream graphs should be condensed down to 1-4
and don't understand the relationship between this graph and the release
version (TODO)

* Removed Global stream w/ promotion -- because the global stream graph we
use subsumes this info

* added HPCC RA and HPL : the first because it's important to us; the
second because it's fairly stable and interesting; FFT could also have
been added, but it seems less stable (and is arguably less "the way
we'd like to do it"

* added thread-ring and pidigits -- the former is now less noisy with
qthreads; the latter is now interesting with GMP on in the nightly
testing

* added NAS EP B, FT A, and IS S -- all of these need more eyes on them
to make sure they're as we like them; but in the meantime they're
fairly noise-free

* added many array performance tests -- I looked for ones that looked
fairly noise-free; I think that maintaining/improving performance for
these is key, so thought they were worth a look

* dynamic iterator -- of the various advanced iters, I chose this one
because it's the one we use most commonly and because it had some
interesting changes lately.

* various scalar idiom C vs. Chapel comparisons -- again, these will
be key to performance and they're fairly noise-free

* compilation time -- grabbed this just so we have some sense of
overall compiler performance from week-to-week without bringing
up Elliot's full suite -- this can serve as a canary to look there.

* memory leaks for examples -- this is something else I'd like to keep
an eye on. I could imagine taking one graph from this suite, but
didn't put in the time to split the one I liked off (probably memory
leaks for examples)

* jacobi AST/generated code size -- something else worth tracking

* no-op -- maybe not worth tracking, but I wanted to err on including
it.

In support of the NPB changes above, I split the sizes we care about
out from the .graph files that contained multiple sizes.