John,
Enable FINE-level logging for Guice's Stopwatch:
Logger stopwatchLogger =
Logger.getLogger(com.google.inject.internal.Stopwatch.class.getName());
stopwatchLogger.setLevel(Level.FINE);
This will log perf #s and tell you at a high level where the time is spent
during injector creation.
Beyond that, I'd use a profiler like YourKit.
Unless you have a ginormous configuration, my guess is something expensive
is happening in one of your modules. 4 seconds sounds excessive. I use Guice
on Android, even going so far as to create a separate injector for each
screen, and startup time hasn't been an issue.
Bob
On Sun, Feb 7, 2010 at 2:17 PM, jd <[email protected]> wrote:
> Hi, I am using Guice with a Google App Engine project but have found
> that the startup time of Guice is killing my app. "Loading requests"
> are very frequent in GAE and need to be fast or your user sits and
> waits. Currently the apps startup time is about 6 seconds and of that
> the Injector takes 4 seconds to build. This is with Stage set to
> Development which did knock about two seconds off the time.
>
> My question is, are there any other tricks to reduce Guice startup
> time. Could some configuration be saved or serialized rather than
> recalculated every time my app spins up a new instance?
>
> Thanks,
>
> John.
>
> --
> 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]<google-guice%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-guice?hl=en.
>
>
--
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.
