Artwork

Content provided by 5by5 Broadcasting. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by 5by5 Broadcasting or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

116: Jittery Moment

51:20
 
Share
 

Manage episode 159029466 series 27172
Content provided by 5by5 Broadcasting. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by 5by5 Broadcasting or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Discussion: Time Profiler

  • But first: a brief rundown of the Instruments UI

    • Toolbar
      • Record/Stop
      • Pause
      • Target Selection
      • Status display
      • Strategy Selection
        • CPU data
        • Instrument data
        • Thread data
      • Detail/inspector toggles
    • Timeline
      • Plots data along the time your app was sampled
      • Can be filtered and zoomed
      • Disclosure arrow can toggle display of just the current run or of all runs in the trace document
    • Detail
      • Contents vary by Instrument, but this will generally be a table with some representation of the sampled data
    • Inspectors
      • Record Settings
      • Display Settings
      • Extended detail (often the heaviest stack trace)
  • What is Time Profiler?

    • An Instrument providing sample-based analysis of an application’s activity
    • Periodically samples the call stack to determine where an app is spending its time
      • These are instantaneous samples. They don’t track the duration of a function call, but rather how many times when sampled was the application currently in said function call.
      • No distinction between a fast function called many times and a slow function called few times
      • Extremely fast functions may not get sampled at all, if they happen to occur in between samples
    • Provides a detail view listing call trees, optionally separated by thread and/or state, allowing the developer to drive down into calls to identify areas that may need to be optimized
      • Weight - Percentage of samples in which a function appeared and an aggregate summary of samples (count * sample interval)
      • Self Weight - Aggregate summary of samples in which the function was at the top of the call stack
      • Symbol Name - The thing represented in the current row (may be a function, method, closure/block, thread, or app)
      • Category
      • Additional columns available:
        • Count
        • Self Count
        • Library

Picks

John

Darryl

Alternative show title suggestions

  • Try harder
  • n squared complexity
  • my code, vs not my code
  • expected or unexpected
  • notion of runs

This episode sponsored by Braintree

  continue reading

100 episodes

Artwork

116: Jittery Moment

iOhYes

published

iconShare
 
Manage episode 159029466 series 27172
Content provided by 5by5 Broadcasting. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by 5by5 Broadcasting or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Discussion: Time Profiler

  • But first: a brief rundown of the Instruments UI

    • Toolbar
      • Record/Stop
      • Pause
      • Target Selection
      • Status display
      • Strategy Selection
        • CPU data
        • Instrument data
        • Thread data
      • Detail/inspector toggles
    • Timeline
      • Plots data along the time your app was sampled
      • Can be filtered and zoomed
      • Disclosure arrow can toggle display of just the current run or of all runs in the trace document
    • Detail
      • Contents vary by Instrument, but this will generally be a table with some representation of the sampled data
    • Inspectors
      • Record Settings
      • Display Settings
      • Extended detail (often the heaviest stack trace)
  • What is Time Profiler?

    • An Instrument providing sample-based analysis of an application’s activity
    • Periodically samples the call stack to determine where an app is spending its time
      • These are instantaneous samples. They don’t track the duration of a function call, but rather how many times when sampled was the application currently in said function call.
      • No distinction between a fast function called many times and a slow function called few times
      • Extremely fast functions may not get sampled at all, if they happen to occur in between samples
    • Provides a detail view listing call trees, optionally separated by thread and/or state, allowing the developer to drive down into calls to identify areas that may need to be optimized
      • Weight - Percentage of samples in which a function appeared and an aggregate summary of samples (count * sample interval)
      • Self Weight - Aggregate summary of samples in which the function was at the top of the call stack
      • Symbol Name - The thing represented in the current row (may be a function, method, closure/block, thread, or app)
      • Category
      • Additional columns available:
        • Count
        • Self Count
        • Library

Picks

John

Darryl

Alternative show title suggestions

  • Try harder
  • n squared complexity
  • my code, vs not my code
  • expected or unexpected
  • notion of runs

This episode sponsored by Braintree

  continue reading

100 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide