N T I A L Things you can do on Runtime performance issues: • --perf-basic-prof-only-functions. • A system tool like Perf Events in Linux. • Spare the traces that are really important in your situation. • Checkout Daniel Khan talk to know how to visualize this data.
N T I A L 20 Strategy for Memory Leaks detection: • Inspect objects for more context. • Look for weird objects on heap • Growing object counts are likely leaking • Walk reverse references to find the root object • Compare object counts !important
N T I A L What is happening? • On the first snapshot, there are already/almost ~7-8MB allocated before any request is processed. • Memory keeps growing while the server is running and getting requests • Date objects and Objects have been allocated and increased between the two load sessions.
N T I A L • As you can see, the memory growth is far slower! • This said, the API takes more time to respond. Reading and writing to the disk comes with a cost, so do other API calls or database requests.
N T I A L Blocking the Event Loop • Totally possible • Happens more times we want it to happen (who wants to block it in first place?) • Iterations and complex calculations would prevent the process from handling other events