Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

photos very high cpu usage

M

mirzank

macrumors regular
Original poster
Apr 15, 2008
225
2
I updated to photos yesterday, and have been seeing some ridiculous cpu numbers, and my macbook pro running really really hot. when photos is open i see cpu usage of 150% by photos, and another 20-30% by a photoslibrary process. photos already migrated my iphotos library when i first started it. i see all my pictures in photos. I don't have icloud photo sync turned on (photostream is on though).

First i thought maybe its because its downloading my photostream pictures, but the thing is i see no network activity. so its already downloaded photstreams. Is photos just a really cpu intensive app and thats why im seeing this huge cpu usage? or is there something going on in the background on the first few runs thats causing high cpu usage?
 
Photos needs to rescan all the pictures to create new previews and for faces too. So it's going to use a bit of cpu until it finishes.
 
I have the same problem, its been running at 150% for over 4 hours. I don't think its going to get better.:mad:
 
Yes! Same here. 150-250% CPU usage on 15" rMBP mid 2014, 1 TB 16GB RAM, 2.5Ghz. Very high energy usage statistics too--and much worse on all counts than Aperture.

Is there a way to verify that it is indeed doing some early-stage "indexing" or making previews of some kind?

Aperture has an activity monitor/task manager that lets you see what it is doing...is there something like this in Photos?

Plus, am I wrong or is there no batch editing/adjustments in Photos?!
 
Plus One

Mine is so bad that it goes up to 200-250%, processor overheats and reboots the machine. Now I can't run the machine for more than 3 minutes with photos running, without a freeze-reboot due to heat.

I have 19,000+ pictures. I looked in Photos Preferences and toggled the "Pause for one day" button to iCloud Photo Library on and off, and it appeared to directly affect processor usage (and as a result fan speed and crashes).

MBP 15"
Early 2011
16gb RAM
250gb SSD
 
wkalexand said:
Mine is so bad that it goes up to 200-250%, processor overheats and reboots the machine. Now I can't run the machine for more than 3 minutes with photos running, without a freeze-reboot due to heat.

I have 19,000+ pictures. I looked in Photos Preferences and toggled the "Pause for one day" button to iCloud Photo Library on and off, and it appeared to directly affect processor usage (and as a result fan speed and crashes).

MBP 15"
Early 2011
16gb RAM
250gb SSD
Click to expand...

while mine hasnt been as bad as to reboot the machine, with 150-160% cpu usage my temperatures go up to 82-83 celcius, and as high as 85-86. thats the point i just shutdown photos cos noway do i want it to run at that temperature for a prolonged period of time!

----------
rhyzome said:
Yes! Same here. 150-250% CPU usage on 15" rMBP mid 2014, 1 TB 16GB RAM, 2.5Ghz. Very high energy usage statistics too--and much worse on all counts than Aperture.

Is there a way to verify that it is indeed doing some early-stage "indexing" or making previews of some kind?

Aperture has an activity monitor/task manager that lets you see what it is doing...is there something like this in Photos?

Plus, am I wrong or is there no batch editing/adjustments in Photos?!
Click to expand...

so this is either a bug, or something going on in the background like indexing/caching, no way can this be normal. I thought maybe it was because of my old'ish mbp - 2010 13 inch with 2.4ghz c2d, 8 gb ram, and ssd just couldnt handle it.but if your latest 2014 mbp with 16GB!! ram is having the same issue then this is definitely not normal
 
I was just going to start a new post about this, I'm running a Core i7 Mac Mini with 10GB ram, and photos is running like a sloth and my machine generally seems to be struggling, I knew I shouldn't have updated so quickly.

I swear this is the last time I update for at least a month after an update comes out. I was going to update my iPad as well, but I'll be waiting at least a month.
 
Hmmm....

Only 15.3% usage here. I only have a few thousand photos however and I'm pretty sure it's done doing it's optimizing thing.

8 gig ram, i5 MBP.
 
I noticed this on my Yosemite test partition. Just browsing the library of 1100 photos (mostly jpegs) takes 150% to 250% CPU.
 
Just have the library opened and scrolled through a few rows.
 

Attachments

  • Screen Shot 2015-04-10 at 9.17.41 PM.png
    Screen Shot 2015-04-10 at 9.17.41 PM.png
    408.8 KB · Views: 815
During the betas my 400GB library took over 24hrs of 200%+ CPU usage.... Then it calmed down and worked. Although the previews/thumbnails it'd generated added an extra 40GB to the library.

2013 2.3GHz i7 MacBook Pro Retina. 512SSD. 16GB RAM.
 
ok good news. my photos app has now settled down. I let it run for about 30 mins at the 150-180% cpu usage, and temps running as high as 82 c. First the usage of photolibraryd went down, then after a little while photos app usage went down. I have about 6k photos in my library.
 
I have the same thing. I've let it run for quite a while and it shows no signs of stopping so far. I'm just going to let it run in the background for the next 6 hours or so to see if it ever finishes whatever mysterious task it's undertaking.

If the theory that it's doing some sort of photo processing (I can't imagine what...) is correct, I'll note here that I have 14,000 photos and 1,000 videos in my library.


One interesting thing is that (if you have a portable Mac), when you unplug from MagSafe, it stops hogging the processor and behaves like a good little app. Give it the juice again and it'll turn straight back into a CPU-gnawing gremlin. Interesting power-save feature.
 
wkalexand said:
Mine is so bad that it goes up to 200-250%, processor overheats and reboots the machine. Now I can't run the machine for more than 3 minutes with photos running, without a freeze-reboot due to heat.
Click to expand...

If your Mac overheats, unless you did something to prevent it from properly cooling, it is defective.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back