-
Musings about Cores and Memory and FCP, Oh My.
I’ve had the Activity Monitor up on my second screen for a few days to see
what was happening with CPU and memory usage. I did this initially because
I was setting up Compressor as a virtual cluster and wanted to see if it was
actually using the other cores, which it is. Amazing to watch how fast
Compressor will do an MPEG2 for a DVD now.But the reason for this post is…
I have an 8 core 3 ghz Mac Pro with 8 gigs of memory.
I notice that with FCP, even when rendering, it never uses more than 500%
of the CPU usage, and usually it’s much less. Typically when rendering
it’s from 150 to 400%. When FCP is playing back footage it’s using a
very small amount, like 36%, or not even one complete core.
And as far as memory goes, I have 8 gigs onboard, but FCP only uses
1.36 gigs of real memory but goes out and grabs 2.3 gigs of virtual
memory on the system drive. This can’t help but slow things down.
Virtual memory is SLOW memory.So, I have to wonder a few things here…
Why can’t Apple get FCP to use more of the Cores for rendering?
I see 50% or more idle CPUs when rendering.
And why go out to the hard drive for memory when I’ve got three times
as much real memory just setting there idle.
And, if during playback while FCP is currently using about 36% of a
single core, what would happen if FCP could be using 7 other cores?
Couldn’t we see real time playback of effects?Just wondering?
Thanks,
Dan