My main concern is that I'm not primarily interested in Cassandra at this point, I'm interested in my JDI project, and formal benchmarking of Cassandra on each item I find is probably more work than I want to put in at this time. If there's an easy benchmark that's already generally agreed upon, I'll be happy to run it first, but otherwise, I'm basically asking if the dev group is interested in reports that won't reach the threshold of having a demonstrated performance impact, or if those kinds of reports are generally just regarded as annoying.
On Fri, Aug 6, 2010 at 4:37 PM, Gary Dusbabek <gdusba...@gmail.com> wrote: > I think if there is a demonstrable increase in performance or other > obvious wins, then you should go ahead and submit jiras (and patches). > > Gary. > > On Fri, Aug 6, 2010 at 15:25, Jason Fager <jfa...@gmail.com> wrote: >> Hi all, >> >> I'm doing some work with the Java Debugger Interface, and I'm using >> Cassandra as a test bed. I've found a few minor contention spots >> (example: MessageDigest.getInstance() being called for every >> invocation of FBUtilities.hash()), but before I start possibly >> spamming your jira with them, I wanted to gauge the general interest >> in knowing these kinds of minor issues. I'm happy to report them as >> they come up while I'm doing my work, but if you consider them too >> minor to worry about until they actually show up as impacting >> performance during profiling, I don't want to annoy anyone. Let me >> know. >> >> - Jason >> >
