Differences
This shows you the differences between two versions of the page.
|
ep:labs:07:contents:tasks:ex4 [2025/02/20 11:52] cezar.craciunoiu created |
ep:labs:07:contents:tasks:ex4 [2025/05/04 03:10] (current) radu.mantu |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== 04. [30p] Perf & fuzzing ==== | + | ==== 04. [25p] Perf & fuzzing ==== |
| The purpose of this exercise is to identify where bottlenecks appear in a real-world application. For this we will use **perf** and American Fuzzy Lop (**AFL**). | The purpose of this exercise is to identify where bottlenecks appear in a real-world application. For this we will use **perf** and American Fuzzy Lop (**AFL**). | ||
| Line 101: | Line 101: | ||
| Make sure to include plenty of screenshots and explanations for this task :p | Make sure to include plenty of screenshots and explanations for this task :p | ||
| - | === [10p] Task C - Flame Graph === | + | === [5p] Task C - Flame Graph === |
| A [[https://www.brendangregg.com/flamegraphs.html|Flame Graph]] is a graphical representation of the stack traces captured by the **perf** profiler during the execution of a program. It provides a visual depiction of the call stack, showing which functions were active and how much time was spent in each one of them. By analyzing the flame graph generated by //perf//, we can identify performance bottlenecks and pinpoint areas of the code that may need optimization or further investigation. | A [[https://www.brendangregg.com/flamegraphs.html|Flame Graph]] is a graphical representation of the stack traces captured by the **perf** profiler during the execution of a program. It provides a visual depiction of the call stack, showing which functions were active and how much time was spent in each one of them. By analyzing the flame graph generated by //perf//, we can identify performance bottlenecks and pinpoint areas of the code that may need optimization or further investigation. | ||
