Prime MVC calls getInstance every request. This is great because all controllers are non-singletons and state doesn't get polluted. Though Guice is rarely the bottleneck for most apps.
-- Brian Sent from my iPhone > On Oct 14, 2014, at 10:59 AM, Kevin Burton <[email protected]> wrote: > > OK.. silly question, why would this matter? > > The performance of Guice didn't seem pathologically broken. > > What I do is just create all my bindings at startup and then I'm done. Any > complex initialization is done via providers... > > So maybe I'm missing something and there are some use cases that people are > calling getInstance() in a more production or tight loop situation? > > Is this an anti-pattern or actually valuable? > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-guice. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-guice/d0227e61-a0bd-40d9-b8db-3aabdc3be423%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. To view this discussion on the web visit https://groups.google.com/d/msgid/google-guice/B42840B2-CB67-4DD9-8A31-1D3F0A9DA417%40pontarelli.com. For more options, visit https://groups.google.com/d/optout.
