> that was happening? I know I could insert my own code to track that, > but it seems like this may be a commonly needed tool for Clojure to > detect excessive conflicts/retries in transactions. Maybe we could set > a special variable like *track-retries* that would cause Clojure to > produce a text file that describes all the transaction retries that > occurred in a particular run of an application. If such a tool isn't > needed or wouldn't be useful, I'd like to understand why.
given what i've heard about Azul running threaded Java code (Clojure might be different, of course!), i think there are insufficient guarantees to make such tools useful. running the same threaded Java code on a different machine has a not-insignificant chance of having quite different scheduling. sincerely. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
