The last I looked it would need to be added at the Java level.
On Fri, Mar 20, 2009 at 5:32 PM, Mark Volkmann wrote:
>
> On Fri, Mar 20, 2009 at 4:02 PM, Jeffrey Straszheim
> wrote:
> > +1
> > I think two simple atomic integers would do the trick:
> > 1. Number of transactions entered
> > 2. N
On Fri, Mar 20, 2009 at 4:02 PM, Jeffrey Straszheim
wrote:
> +1
> I think two simple atomic integers would do the trick:
> 1. Number of transactions entered
> 2. Number completed, or exited through exception.
> The amount 1 exceeds 2 is your retry rate.
Right. I could implement this myself in
+1
I think two simple atomic integers would do the trick:
1. Number of transactions entered
2. Number completed, or exited through exception.
The amount 1 exceeds 2 is your retry rate.
On Fri, Mar 20, 2009 at 4:38 PM, Mark Volkmann wrote:
>
> It seems that an important part of optimizing the
It seems that an important part of optimizing the performance of a
Clojure application may be to attempt to minimize the number of
retries that are performed in transactions. What are good ways to
detect and count retries other than explicitly adding code inside
dosync calls to count them?
--
R.
