performance tests need work

[bpsm]

Commit 7e5bd61 merges an expanded performance-test branch to master, but this still needs work.

• It's obvious that I don't know my way around Caliper, so I imagine potential improvements would become apparent by investing some time in learning that better.
• Ideally, I'd like the benchmark results to provide results as characters/second, but I have no idea how I might go about doing that with caliper.
• currently, benchmark times include the overhead of opening and closing the reader as well as the associated IO of the underlying characters. That has advantages, since it exercises the more complex of the two Parseable implementations. OTOH, parsing directly out of a String already in memory would produce less variable results.
• I've not added performance tests for Printing. Printing itself is still in an early implementation, but it would be good to get something in place for detecting performance changes there too.

[aadrian]

@bpsm Caliper seems abandoned.

[bpsm]

Yea, I have been considering ripping all that stuff out anyway. The performance testing was useful in early development as a guard against doing anything too stupid performance wise, but I don't use it anymore.

…

-- This message was sent via electromagnetism.

On 13 May 2017, at 21:48, aadrian ***@***.***> wrote: @bpsm Caliper seems abandoned. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[aadrian]

@bpsm The idea of the micro-benchmark is quite interesting, but unfortunately that google project seems abandoned (only the Android part got some updates), and nobody there is merging PRs or making releases :( .

Maybe one could find some alternatives that are not abandoned.