As far as I know the external tools exposed so far are the only way to get the breakdown you are seeking.
Profiling in dev with an external tool is kind of a conflicting goal to me. Such tools used in dev are also a form of micro benchmarking on incomplete code. Your app is not fully packaged, how meaningful are the hot spots you may find at this stage ? What does it tell you about the future behaviour of your app ? With the REPL in the way reevaluating code as you modify it ? Criterium allows us to evaluate at any level in our code if the performance is acceptable or not. It does a sane job collecting stats. I can exercise 5% or 50% of the code and get stats from its execution within a couple of minutes with the workload size I desire. I can do minute changes and see the effect. If the performance is satisfactory, no need to dig for a hot spot at this stage. We look at hotspots when the app packaging is near completed in test. Then its behaviour is much closer to production. But we rarely find a performance issue justifying a code change except if it's trivial. It's a matter of putting some reasonable effort toward optimization when justified. Doing this early in dev with a time efficient tool to me is a better use of my time than using a sophisticated one requiring some complex wiring from my part. Luc P. > On Sunday, October 5, 2014 4:58:04 PM UTC-4, Luc wrote: > > > > Have a look at criterium. > > > > https://github.com/hugoduncan/criterium > > > > That's (micro)benchmarking, not profiling. Profiling would break down the > time spent in different functions and help to identify hot spots that might > especially benefit from optimization. > > -- > 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 > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Luc Prefontaine<lprefonta...@softaddicts.ca> sent by ibisMail! -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
