On Fri, Mar 18, 2011 at 11:46 AM, Timothy Baldridge <tbaldri...@gmail.com> wrote: >> I'm open to suggestions on improving this. In particular, more >> detailed profiling information would be of interest. > > Hrm...we have some fairly detailed profilers through my work, so I'll > have to fire it up over lunch and see what I get. > > timothy > > -- > 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 > Note that posts from new members are moderated - please be patient with your > first post. > 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 >
I've had a similar issue unrelated to clojure. In my case we had some signed assemblies and the CLR was taking a long time, in certain environments, to go out and check for certificate revocations when verifying signatures. IIRC, the initial profiling I did made it look like the time was spent JIT-ing though it wasn't. I've not played at all with clojure-CLR at this point so I don't know if my experience helps or is related to this issue. -stt -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
