Daniel Khan
where else to find them
what they talk about
where they keep going back
- NodeConf Argentina2 editions2017–2018
all 4 in the filters
on a stage with
never shared a talk
who talks about the same things
- Lorenzo Pieri4 talks
- Tamar Twena-Stern10 talks
- Anna Henningsen17 talks
- Thomas Watson16 talks
- Alejandro Oviedo García6 talks
- Benjamin Cavy11 talks
| title | conference | date |
|---|---|---|
| Tracing Node. The Open Source Edition | JSConfCO 2018 | 2018-11-16 |
Node alone doesn’t guarantee flawless code execution with stellar performance and finding problems in distributed systems is hard. Tracing gives you both… | ||
| Tracing Node. The Open Source Edition. | NodeConf Argentina 2018 | 2018-10-18 |
A demo app (a taps versus spaces voting page) produces a reproducible memory leak sawtooth from PM2 restarts and the talk shows how to collect response times… | ||
| Everything I Thought I Knew about the Event Loop Was Wrong | NodeConf Argentina 2017 | 2017-10-26 |
The event loop is not a separate thread but part of the single JS thread and libuv uses a libuv thread pool of four threads for only certain OS-blocking work… | ||
| Welcome to Mordor! Hunting Performance Issues in Node.js. | Codemotion Amsterdam 2016 | 2016-05-11 |
Shows concrete diagnostics: use V8 metrics (process.memoryUsage, heap snapshots via v8-profiler) and load them into Chrome devtools to spot leaks caused by… | ||
| Welcome to Mordor! Hunting Performance Issues in Node js | Codemotion Rome 2016 | 2016-03-18 |
Covers concrete debugging steps: use process.memoryUsage, V8 heap snapshots and CPU profiles via the V8 API, serialize snapshots and inspect them in Chrome… | ||
| nothing matches | ||