PurePerformance 035 When Multi-Threading, Micro Services and Garbage Collection Turn Sour
May 8, 2017
47:31
For our one year anniversary episode, we go “back to basics”, or, better said, “back problem patterns”.
We picked three patterns that have come up frequently in recent “Share Your PurePath” sessions from our global user base and try to give some advice on how to identify, analyze and mitigate them:
· Bad Multi-threading: Multi-threading is not a bad thing – but if done wrong it doesn’t allow your application to scale. We discuss key server metrics and how to correctly read multi-threaded asynchronous PurePaths. Also see the following blog: https://www.dynatrace.com/blog/how-to-analyze-problems-in-multi-threaded-applications/
· When Micro Service become Nano Services. This was inspired by a blog from Steven Ledoux ( https://www.dynatrace.com/blog/micro-services-when-micro-becomes-nano/ ). It's important to keep a constant eye on your micro-service architecture to avoid too tightly coupled or too fine grained architectures
· Garbage Collection Impact: GC is important but bad memory management and heavy GC can potentially impact your critical transactions. We discuss different approaches on how to correctly measure the impact of garbage collection suspension. If you want to learn more check out the Java Memory Management secton of our online performance book: https://www.dynatrace.com/resources/ebooks/javabook/impact-of-garbage-collection-on-performance/
We picked three patterns that have come up frequently in recent “Share Your PurePath” sessions from our global user base and try to give some advice on how to identify, analyze and mitigate them:
· Bad Multi-threading: Multi-threading is not a bad thing – but if done wrong it doesn’t allow your application to scale. We discuss key server metrics and how to correctly read multi-threaded asynchronous PurePaths. Also see the following blog: https://www.dynatrace.com/blog/how-to-analyze-problems-in-multi-threaded-applications/
· When Micro Service become Nano Services. This was inspired by a blog from Steven Ledoux ( https://www.dynatrace.com/blog/micro-services-when-micro-becomes-nano/ ). It's important to keep a constant eye on your micro-service architecture to avoid too tightly coupled or too fine grained architectures
· Garbage Collection Impact: GC is important but bad memory management and heavy GC can potentially impact your critical transactions. We discuss different approaches on how to correctly measure the impact of garbage collection suspension. If you want to learn more check out the Java Memory Management secton of our online performance book: https://www.dynatrace.com/resources/ebooks/javabook/impact-of-garbage-collection-on-performance/