Dagger 2 metrics
If you use Dagger 2 for dependency injection in your Android app you probably know that it's super optimized and non-reflection piece of code served by great engineers from Google (and formerly from Square).
Even with all those optimizations and fully generated non-dynamic code, still there are potential performance issues hidden in our code and all 3rd parties injected via Dagger 2.
The problem with performance is that it often decreases slowly so in day-by-day development it's hard to notice that our app (or Activity or any other view) launches 50ms longer. And another 150ms longer, and another 100ms...
With AndroidDevMetrics you will be able to see how much time was needed to initialize all requested dependencies (and dependencies of those dependencies).
Dagger2Metrics captures all initializations from both - @Module -> @Provides annotated methods and @Inject annotated constructors.
In summary you will see the most-top injected dependencies with trees of their dependencies. Each of dependency shows how much time was needed to provide this object to Dagger 2 object graph (construction time itself and overall time with all dependencies).
Metric trees don't show dependencies which are already provided to Dagger's graph, so only those constructed from scratch will be visible. Mainly because of readability and from a simple reason - we don't want to measure Dagger 2 performance which in most cases won't be an issue.
Instead we should be sure that our code provides requested dependencies as fast as it's possible.
You can adjust them to your needs.
You can check GithubClient project - example Android app which shows how to use Dagger 2. Most recent version uses AndroidDevMetrics for measuring construction times.
If you're just starting with Dagger 2, here is the list of resources which can help you with it:
GithubClient - example of Github API client implemented on top of Dagger 2 DI framework.
Blog posts: