I think the best bet is really to attach a profiler like yourkit / mission control etc and check if the IO threads are blocked at some point and on which method calls.
Bye, Norman > On Nov 11, 2017, at 06:02, Alberto Klocker <[email protected]> wrote: > > Hi All, > > As we all know blocking code is cryptonite to async event loops, I was just > wondering what techniques and profilers are best for finding code that should > be moved to its own executor. > > As one of the Youtube talks Norman gave a few years ago, something as > innocent as a DNS lookup in the main pipeline can jam things up. > > > -- > You received this message because you are subscribed to the Google Groups > "Netty discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/netty/CAGrhr76UDah-QWr%3DE8ZZHD0Fp4aEC5EG9KSDOrzbXWueg6pTEg%40mail.gmail.com > > <https://groups.google.com/d/msgid/netty/CAGrhr76UDah-QWr%3DE8ZZHD0Fp4aEC5EG9KSDOrzbXWueg6pTEg%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/54F1CD17-7BA5-49D5-AC20-7898CBB97A09%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
