On Thu, Apr 9, 2009 at 1:23 PM, Onorio Catenacci <catena...@gmail.com> wrote:
> [..] > > I know you were mentioning some real performance issues when starting > a Clojure app from Android (I see them too). I wonder if using > TraceView to profile the Dalvik code generated by the conversion from > the Clojure bytecode might point us to something to fix the startup > time? I'll try this myself--I just thought I might ask you if you'd > already done this and if it were a waste of time or not. :-) I've used the mentioned profiler and I did some performance tweaks already, thus the clojure fork on github. The "original" startup time of an application was around 15 seconds and using the current fork it's about 5 seconds. Still too much IMO. Most of the startup time is spend bootstrapping the clojure core. Unfortunately the profiler doesn't give any clear suspects any more, so I need to figure out another way to speed this up. Maybe doing something like a core dump after bootstrap and making that executable in some way is a solution but that goes beyond my knowledge of the internals of clojure and java byte code generations at this moment. Can anybody give me pointers? Remco --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
