Return to Video

Untitled

  • 0:00 - 0:04
    So the answer we're looking for here is
    actually the computeFibonacci method.
  • 0:04 - 0:06
    So let's review what I
    did to figure it out.
  • 0:06 - 0:11
    All right, so running Traceview on
    the following activity, and basically
  • 0:11 - 0:15
    profiling the function that happens when
    I press this compute Fibonacci function.
  • 0:15 - 0:17
    This is what the Traceview
    output looks like.
  • 0:17 - 0:20
    All right, so here's an output
    that I got from running Traceview.
  • 0:20 - 0:22
    You should see something similar.
  • 0:22 - 0:24
    Notice this large pink area.
  • 0:24 - 0:26
    This is a bad thing, this basically
    indicates that something is
  • 0:26 - 0:30
    taking up a lot of CPU
    time on our main thread.
  • 0:30 - 0:35
    So if you sort by exclusive CPU time,
    or by hovering over this pink area.
  • 0:35 - 0:39
    You'll notice that the computeFibonacci
    method, which is coming from our caching
  • 0:39 - 0:42
    activity, is the one that's actually
    occupying the most CPU resources.
  • 0:42 - 0:44
    So this is something we want to fix
Title:
Untitled
Description:

03-05 BatchCache Observe, Profile, Analyze

more » « less
Video Language:
English
Team:
Udacity
Project:
ud825 - Android Performance
Duration:
0:45

English subtitles

Revisions Compare revisions