accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joshelser <...@git.apache.org>
Subject [GitHub] accumulo issue #244: Discuss ACCUMULO-3079: collapsing the iterator stack to...
Date Tue, 11 Apr 2017 16:51:31 GMT
Github user joshelser commented on the issue:

    https://github.com/apache/accumulo/pull/244
  
    > Any ideas how we would record benchmarks? Have them run with the release plugin?
Then publish with release notes?
    
    I'm hesitant to suggest publishing them with release notes as the "norm". I'd think that
we could just start a new part of the website to capture this (since they are likely only
developer-related). If we feel like it is worthy of mentioning in the release notes (e.g.
the numbers are not misleading or context-specific), then we can do so. Otherwise, the website
can just serve as the record of "results". We could expand this out to include things like
ContinuousIngest numbers too (which would be awesome -- don't have to build up a list of numbers
from release notes..)
    
    > We should also discuss alternatives to JMH. I only chose it because it was the first
one you suggested. FYI I haven't been able to get the setup() and teardown() annotations to
work.
    
    Heh. I think I played around with JMH once. For the most part, I think JMH and Caliper
are pretty equivalent in terms of functionality. @matthew-dailey, didn't I talk to you about
this a long time ago and you had some experience with them both?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message