Brendan Gregg focuses on broken tools and metrics instead of the working ones. Metrics can be misleading, and counters can be counter-intuitive. He advises on how to approach new performance tools.
Cliff Click takes a look at Java vs C performance. He discusses both languages' strong and weak points and the programming context surrounding language choices.
Nitsan Wakart discusses concrete cases in which profilers misguide, misrepresent and at times subvert the systems they aim to help us diagnose.
Todd Montgomery discusses the challenges of I/O, as software and hardware change rapidly and conventional wisdom must evolve to keep up, revisiting old ideas with new and different perspectives.
Phillip Trelford shows through live demos data structures that are orders of magnitude more performant than lists.
Ben Watson provides a deep-dive introduction to what you need to know to squeeze out the ultimate performance from your .NET code, along with war stories from building the Bing platform query engine.
S Maldini, G Renfro and D Turanski dissect a Spring XD app to show design patterns and techniques for getting the highest throughput and lowest resource utilization in streaming apps.
Yongsheng Wu talks about how to build highly-resilient systems at scale. Wu presents also failure cases that prompted engineers at Pinterest to build such systems, and how they test these systems.
Ian Cooper looks at Service Discovery and Clustering approaches and tools, and shows .NET developers how to work with tools such as Serf, Consul, and Zookeeper.
Yves Reynhout discusses models, how they're created and tested against scenarios, how they're useful, what distinguishes them from others, how they're visualized and communicated, etc.
Itamar Syn-Hershko shows using various technologies -Storm, Node.js, Riemann, collectd, D3.js, ELK, PagerDuty, Slack - to power Forter’s service and keep it highly available and under control.
Charlie Hunt explains the three performance attributes of throughput, latency and (memory) footprint and how each of these are influenced in terms of JVM garbage collection.