"Shark analysis" here seems to refer to the usage of the "Shark" tool: https://www.cs.tufts.edu/comp/150PAT/tools/shark/SharkUserGuide.pdf https://www.cs.tufts.

"Shark analysis" here seems to refer to the usage of the "Shark" tool: https://www.cs.tufts.edu/comp/150PAT/tools/shark/SharkUserGuide.pdf https://www.cs.tufts.edu/comp/150PAT/tools/shark/SharkUserGu.... From the PDF: > Shark is a tool for performance understanding and optimization. To help you understand the performance of your code, Shark allows you to profile the entire system (kernel and drivers as well as applications). This information is an invaluable first step in your performance tuning effort so you can see which part of your code or the system is the bottleneck. > At the simplest level, Shark profiles the system while your code is running to see where time is being spent. It can also produce profiles of hardware and software performance events such as cache misses, virtual memory activity or instruction dependency stalls. I had no idea what it was, so I'm sharing it here for others.