Exporting from iMovie leads to heavy TMG CPU load
Robert Brewer
that TimeMachineGrowler is using substantial CPU. Every few seconds it
jumps to 2nd place just under iMovie, runs for a few seconds, then CPU
usage drops and the cycle repeats. I've only observed this when iMovie
is exporting a movie.
Any thoughts? Running TMG 1.0.1 on Mac OS X 10.6.4 on a Unibody
MacBook Pro 15"
Peter Hosey
> … I noticed in Activity Monitor that TimeMachineGrowler is using substantial CPU. Every few seconds it jumps to 2nd place just under iMovie, runs for a few seconds, then CPU usage drops and the cycle repeats.
Correct. TimeMachineGrowler works by searching the Console log, and this is currently a CPU-intensive operation. Depending on how many messages you have in your Console log, it can be over quickly, take a few seconds, or even (in extreme cases) bog down for taking so long.
> I've only observed this when iMovie is exporting a movie.
That doesn't make a difference. You should notice the cores light up every ten seconds regardless.
Robert Brewer
You are quite right, I guess I just didn't notice it before. Is there a way
to make it scan the Console log less frequently? I think I'd be pretty
happy with scans happening every 30 or 60 seconds.
Peter Hosey
> Is there a way to make it scan the Console log less frequently?
It's hard-coded, so the only way is to download the source code, change the poll interval there, build it, and run your custom build. This, of course, requires the developer tools.