Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

CPU usage of C1

picman2
I am flabbergasted. I've got a new 6 core 3,33 GHz MacPro with 16GB RAM (see advice Diglloyd) and I opened up the Activity Monitor to see what kind of CPU usage a normal C1 session would have. There are 12 processors (hyperthreading) shown. When I open a session and simply go from one picture to the next (raw Alpha900), all 12 processors jump to 70 up to 100% and stay there for about 1-2 seconds! I also have Protools and lots of audio applications on that same computer and with heavy sessions (say 12 virtual instruments + 12 audio tracks playing back from the internal hard disk + lots of plugin processing) I never see that kind of CPU usage, never do the processors go above the 1/3 mark. I've looked at LR3, DxO and Aperture too, and whereas they all seem to be a bit more hungry than audio applications I never saw that kind of CPU usage.

Cheers, Bob.
0

Comments

5 comments

Date Votes
  • thowi
    And?
    Only shows that C1 utilizes CPUs as much as possible. Basically a good thing!
    0
  • picman2
    [quote="thowi" wrote:
    And?
    Only shows that C1 utilizes CPUs as much as possible. Basically a good thing!


    Oh come on. You very well know what I mean and this is no answer at all. I am surprised that heavy (and I mean really heavy) audio software only requires about 1/3 of the CPU power when running, but that switching from one photo to the next one in C1 requires full blown capacity. Is it so strange that I wonder why? If someone has a reasonable explanation I'd like to hear it.
    0
  • Paul Steunebrink
    Other information I would consider relevant in such a conversation: version of CO, OpenCL state, resolution of monitor, preview image size, over exposure warning state, focus mask, focus window. To get the picture, if you understand.
    0
  • picman2
    [quote="Paul_E" wrote:
    Other information I would consider relevant in such a conversation: version of CO, OpenCL state, resolution of monitor, preview image size, over exposure warning state, focus mask, focus window. To get the picture, if you understand.


    I understand.

    C1 v 6.0
    OpenCL: never
    30'' Cinema Display 2560x1600
    preview image size: 1800, raw files 38MB, physical size of window maximal fit of display approx 2200x1400
    no over exposure warning
    no focus mask
    no focus window

    What seems clear is that C1 is nicely using all cores evenly.
    0
  • Dana Neibert
    [quote="picman" wrote:
    [quote="Paul_E" wrote:
    Other information I would consider relevant in such a conversation: version of CO, OpenCL state, resolution of monitor, preview image size, over exposure warning state, focus mask, focus window. To get the picture, if you understand.


    I understand.

    C1 v 6.0
    OpenCL: never
    30'' Cinema Display 2560x1600
    preview image size: 1800, raw files 38MB, physical size of window maximal fit of display approx 2200x1400
    no over exposure warning
    no focus mask
    no focus window

    What seems clear is that C1 is nicely using all cores evenly.



    Agreed. I would be pissed if only one core was being used to do all that work.
    0

Post is closed for comments.