cc_staff
782
edits
OpenACC Tutorial - Profiling: Difference between revisions
Jump to navigation
Jump to search
Reviewed introduction to profiling
(Marked this version for translation) |
(Reviewed introduction to profiling) |
||
| Line 14: | Line 14: | ||
}} | }} | ||
<translate> | <translate> | ||
== Code profiling | == Code profiling == <!--T:8--> | ||
Why would one need to profile code? Because it's the only way to understand: | Why would one need to profile code? Because it's the only way to understand: | ||
* Where time is being spent ( | * Where time is being spent (hotspots) | ||
* How the code is performing | * How the code is performing | ||
* Where to focus your time | * Where to focus your development time | ||
<!--T:9--> | <!--T:9--> | ||
What is so important about hotspots in the code ? | What is so important about hotspots in the code? | ||
Amdahl's law says that "Parallelizing the most time-consuming routines (i.e. the hotspots) will have the most impact". | Amdahl's law says that "Parallelizing the most time-consuming routines (i.e. the hotspots) will have the most impact". | ||