ThreadScope Tour/Zoom

From HaskellWiki
< ThreadScope Tour
Revision as of 19:48, 9 December 2011 by EricKow (talk | contribs) (remove bookmarking and focus on the GC stuff)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Use zooming to reveal more detailed performance issues


  1. Open the sudoku3 ThreadScope profile created earlier

    threadscope ./sudoku3.eventlog
  2. Notice the initial lack of activity at the very beginning of program execution

    Ramping up

    What's going on there?

  3. Use the zoom in button to explore that space a bit more

    Hint: you can also press +/- on the keyboard

    Zooming in

    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.

  4. While you're zoomed in, observe the link between activity and garbage collection.

    Activity ceased during 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.


  • You can also press +/- on the keyboard to zoom in and out