(→Steps: tidy up use of images)
(remove bookmarking and focus on the GC stuff)
|(5 intermediate revisions by one user not shown)|
Latest revision as of 19:48, 9 December 2011
 1 Objective
Use zooming to reveal more detailed performance issues
 2 Steps
Open the sudoku3 ThreadScope profile created earlier
Notice the initial lack of activity at the very beginning of program execution
What's going on there?
Use the zoom in button to explore that space a bit more
Hint: you can also press +/- on the keyboard
Notice how different the profile looks close up. What do you see? At closer inspection what looks like a moderate amount of activity is actually intense bursts using both cores, with pauses in between.
While you're zoomed in, observe the link between activity and garbage collection.
Understanding your program's performance may require looking at different resolutions, zoomed out to get the overall feel, and sometimes zoomed in to notice finer patterns like these tiny bursts of work with interleaved garbage collection.
 3 Hints
- You can also press +/- on the keyboard to zoom in and out