Right now there are just a couple. It sounds like there's enough interest, so
I'll just add them as they come up, and if it starts to be alot, I'll start
coalescing them.
Thanks,
Jason
On Aug 6, 2010, at 5:19 PM, Jeremy Hanna wrote:
> Are you talking about a handful of issues or a large
Are you talking about a handful of issues or a large number of issues?
If it's the former, then a Jira issue for each isn't unreasonable. If it's the
latter, maybe all of your results could go into one Jira issue with steps to
reproduce your results. Then someone could do some more investigati
On 8/6/10 1:37 PM, Gary Dusbabek 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).
+1, when you have hundreds of threads, even minor contention issues may
be significant.
=Rob
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
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 wrote:
> Hi all,
>
> I'm doing some work with the Java Debugger Interface, and I'm using
> Cassandra as a tes
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
