On Jun 20, 2012, at 9:11 AM, glenviewjeff wrote: > Christian, 95% of the startup code is Guice binding code; and there's zero > I/O, database/network operations, etc. If you're an Android developer, (or > even if you're not but are willing to install the Android tools so you can > use Traceview), I can send you the tracing file if you'd like to see for > yourself. >
Not an android guy (and am in the middle of six things - won't be able to start up a new environment for this - but I trust you). Reflection can be expensive in constrained environments. I am hoping to do some benchmarking with caliper this coming quarter, and look at key areas to speed up. As a personal musing, I wonder where most of that work is… the reflection of finding @Inject constructors and using them, or of looking up provider methods. etc. Which bits would be the biggest hits. And byte code manipulation might not be faster for your case, but a code-gen approach might. While I can't setup the env right now, when I start benchmarking, it'd be good to look at this. Please feel free to send me the trace-view, and I'll dig through it when I can get some time for this. C. -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
