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 <r.mark.volkm...@gmail.com>wrote:
> > On Fri, Mar 20, 2009 at 4:02 PM, Jeffrey Straszheim > <straszheimjeff...@gmail.com> 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 every transaction, but I'm > looking for tools that do this or something provided with Clojure ... > this is if such a thing exists. > > > On Fri, Mar 20, 2009 at 4:38 PM, Mark Volkmann < > r.mark.volkm...@gmail.com> > > wrote: > >> > >> 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. Mark Volkmann > Object Computing, Inc. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
