Ece 459 Lecture 28 Cachegrind

The last of the Valgrind tools we will cover is the sadly non-Norse-named Causal profiling allows for running a what-if kind of assessment to understand the impact -- positive, negative, or none at all -- of ... We'll learn about Massif, the heap profiler in the Valgrind toolset, and its newer alternative, DHAT. In our last hardware-focused topic, we'll consider how CPUs that share main memory but have individual caches can all manage ... Are you tired of grinding leetcode? I mean, who isn't? Here, we'll discuss a bit about algorithmic complexity. This isn't about how ... Sometimes how fast we can go is not really under our direct control, so we'll have to get creative about what we can do to work ...

Finally, we're ready to talk about profiling tools -- identifying what's slow in the program. Building on our understanding of borrowing, here we discuss the concepts of threads and traits in Rust. We'll learn about Valgrind, which although is much more intended for languages like C/C++, can still be put to use in Rust in ... We can use the profiler to help the compiler make good decisions when compiling; let's find out how! Continuing our hardware discussion, we'll talk about cache misses and why they're so expensive in terms of performance. This is a brief introduction to the course and a tiny little bit about me.

This is a look into how parallelism really helps us get things done, the limits of it, and how we might move beyond them.