There are a number of interesting and useful stories from enterprise Java and Javascript workloads - ranging from common memory tuning issues that affect the traffic efficiency, to extremely complex multi-thread race conditions leading to application crash, these exciting stories provide vital insights on the platform's interactions with common workloads. The session aims to bring insightful production anomalies, covering how the problem manifested, how we tracked those down, and what lessons were learned.

The outline of this talk is in this format: Problem symptom, business impact, diagnostic data, debugging experiments, root cause, the key learnings and best practices for these stories, each one representative of a symptom class:

• Unexpected large memory retention[ Memory ]
• Slow I/O due to libuv throttling [ low cpu / Performance ]
• Libuv tight loop / high CPU with UDS unplugged [ high CPU ]
• Child process data stream bifurcation [ Functional issue ]
• Crash on exit (aka exit race) [ Crash ]