FROM : Bill Bumgarner
DATE : Mon Jan 07 19:25:19 2008
On Jan 7, 2008, at 10:01 AM, Lorenzo wrote:
> Well, I have checked the CPU % with "top" on the Terminal and during
> the
> playback my app gets 44% of the CPU. If I comment the 3 lines of
> code here
> above, the CPU % goes down dramatically to 3.6%. Even if I comment
> the line
> setMarkerLocation only it goes to 3.6%.
> I have verified with "Quartz Debug" that the "yellow" region of the
> NSRulerView I refresh is just the one under the timeMarker. I am
> sure I am
> making something wrong, because that 44% value is really to much, so
> please
> where should I look at to catch my bug?
Top is pretty useless for finding short duration performance
issues. At best, top can tell you that an app is consuming way too
much resources over longer periods. For shorter intervals, top may
indicate that there is a problem, but you'll need to use other tools
to figure out what it is.
For further analysis, I would suggest using Shark or Instruments to
determine what is actually using the CPU and for how long in the
presence of said code.
b.bum
DATE : Mon Jan 07 19:25:19 2008
On Jan 7, 2008, at 10:01 AM, Lorenzo wrote:
> Well, I have checked the CPU % with "top" on the Terminal and during
> the
> playback my app gets 44% of the CPU. If I comment the 3 lines of
> code here
> above, the CPU % goes down dramatically to 3.6%. Even if I comment
> the line
> setMarkerLocation only it goes to 3.6%.
> I have verified with "Quartz Debug" that the "yellow" region of the
> NSRulerView I refresh is just the one under the timeMarker. I am
> sure I am
> making something wrong, because that 44% value is really to much, so
> please
> where should I look at to catch my bug?
Top is pretty useless for finding short duration performance
issues. At best, top can tell you that an app is consuming way too
much resources over longer periods. For shorter intervals, top may
indicate that there is a problem, but you'll need to use other tools
to figure out what it is.
For further analysis, I would suggest using Shark or Instruments to
determine what is actually using the CPU and for how long in the
presence of said code.
b.bum
| Related mails | Author | Date |
|---|---|---|
| Lorenzo | Jan 7, 19:01 | |
| Bill Bumgarner | Jan 7, 19:25 | |
| Alastair Houghton | Jan 7, 19:25 |






Cocoa mail archive

