Photoanalysisd mac os �������

Что такое «фотоанализ» и почему он использует 77% моего процессора?

Мы получили новый iMac на Рождество, и последние пару дней он казался очень медленным. В отчаянии я проверил Activity Monitor, и он показывает photoanalysisd как виновный процесс, который загружает мой процессор. Я предполагаю, что это связано с приложением «Фотографии», но оно даже не запущено!

Что такое «фотоанализ», почему он использует 77% моего процессора, и могу ли я безопасно остановить процесс?

В настоящее время ваш iMac обрабатывает фотографии в вашей библиотеке фотографий, возможно потому, что вы только что импортировали / конвертировали существующую библиотеку фотографий из более ранней версии macOS.

Если вы подозреваете, что это стало причиной вашей медлительности в течение нескольких дней, то, скорее всего, у вас очень большая библиотека фотографий, и она впервые обрабатывается на вашем новом iMac.

Тот факт, что Photos не работает, в действительности соответствует вашему сценарию, так как запуск приложения Photos приостановит работу photoanalysisd демона.

Хотя это и занимает много времени, после того, как приложение Photos будет выполнено, оно сможет выполнять множество расширенных функций благодаря обработке всех метаданных и т. Д., Поэтому я позволю ему завершить то, что он делает.

НОТА:

Если вам нужно приостановить процесс, чтобы освободить часть вашего процессора, я бы порекомендовал просто открыть приложение «Фотографии» на некоторое время, а затем закрыть его, когда вы не используете компьютер. Тем не менее, обратите внимание, что сворачивание приложения Photos приведет к перезапуску photoanalysisd демона, поэтому просто оставьте его работать в фоновом режиме, пока вы хотите, чтобы демон был приостановлен.

Источник

Что такое «фотоанализ» и почему он использует 77% моего процессора?

Мы получили новый iMac для Рождества, и за последние пару дней он казался очень медленным. В отчаянии я проверил Activity Monitor и показал photoanalysisd как виновный процесс, который забивает мой процессор. Я предполагаю, что это связано с приложением «Фотографии», но это даже не работает!

Что такое «фотоанализ», почему он использует 77% моего процессора и могу ли я безопасно остановить процесс?

4 ответа

В настоящее время iMac обрабатывает фотографии в вашей библиотеке фотографий, по-видимому, потому, что вы только что импортировали /преобразовали существующую фотографию из более ранней версии macOS.

Если вы подозреваете, что это была причина вашей медлительности на пару дней, то, скорее всего, у вас очень большая библиотека фотографий и что она обрабатывается в первый раз на вашем новом iMac.

Тот факт, что Фотографии не работает, действительно соответствует вашему сценарию, поскольку запуск приложения «Фото» приостанавливает демон photoanalysisd .

Хотя это займет много времени, как только оно будет завершено, ваше приложение Photos сможет выполнить множество расширенных функций из-за всех метаданных и т. д., которые будут обработаны, поэтому я позволил бы ему закончить то, что он делает.

Примечание:

Если вам нужно приостановить процесс, чтобы освободить часть вашего процессора, я бы рекомендовал просто открыть приложение «Фото» некоторое время, а затем выйти из него, когда вы не используете компьютер , Обратите внимание, однако, что сведение к минимуму приложение Photos будет действовать для перезапуска демона photoanalysisd , поэтому просто оставьте его в фоновом режиме, пока вы хотите, чтобы демон приостановился.

Открытие фотографий не приостанавливает фотоанализ, будь то на заднем плане или переднем плане.

Это просто приводит к как фотоанализу, так и photolibraryd, потребляющему процессор.

Могу ли я предложить использовать App Tamer ?

Он позволяет приостановить /остановить процесс, когда он достигнет% от времени процессора.

Поскольку я использую его, моя температура компьютера всегда довольно низкая.

Надеюсь, что это поможет!

P.S .: Я не являюсь аффилированным лицом с App Tamer. Я просто счастливый клиент!

У меня есть только дюжина фотографий в моей библиотеке (это мой запасной компьютер, мои фотографии находятся на моем основном компьютере), и я разрешил процесс работать в течение недели, и он все еще питается 100% оба ядра. Моя машина не реагирует на процессорный вентилятор на 100% (13-дюймовый MacBook Pro Mid-2010). Ни одно из решений, которые я нашел в Интернете, не было, я, наконец, временно переименовал свою библиотеку фотографий, чтобы скрыть ее от деамона, и мгновенно Процессоры идут от 100% до 5%.

Источник

Controlling photoanalysisd

Background

I recently bought a new MacBook. This article gets better, I promise.

I decided to set it up fresh instead of restoring from a backup. I like to take the time to try and simplify what I’ve got on my machine.

Naturally, I expect most applications to take a little bit to sync down settings, files, etc. All of Apple’s stuff in particular has a lot to do and I’m fine with that. However, the one I am not so fine with is Photos.

Specifically, a process called photoanalysisd .

This is a background service that, as the name implies, is responsible for analyzing your photos. For the most part, it seems like it is trying to recognize people. This service is directly tied to the «People» tab in Photos (more on this in a moment).

The fact that this happens on your machine and each of your machines is a good thing! There may be some things that get sent off to Apple, but the majority of the work seems to be happening on your hardware.

What is not so good is the level of control you have around if/when/how this service is controlled. Or, in this case, how it seems to control your machine.

If you go into the People tab of Photos before it is done analyzing, you will see its progress. Even if you have a fairly beefy machine, this process takes a long time. Weeks kind of long time. The only exception seems to be if you have a photo library barely into or lower than quadruple digits.

On the surface, this shouldn’t be an issue. The sorts of analysis its doing is probably computationally intense. It uses a good amount of resources, but doesn’t try to fully harness the machine since it is meant to be a background process that occurs over the course of days.

The main issue seems to be that you have no control over this process. I never plan to use the People tab, yet my machine still has to painstakingly go through my entire library. I have a medium size photo library (

10k) and after a few hours on the 12″ i5 MacBook, it has managed to go through almost 300 of them. Many people complain about their way more powerful iMacs taking weeks to go through libraries of similar size.

During this process, the machine is still usable, but it doesn’t go unnoticed. It does use about 25% of the CPUs constantly. This causes the fanless machine to constantly stay pretty warm and chug on some things. Usually not enough to notice, but seems like it might cause someone to be less than impressed with their brand new device if they didn’t know this was going on.

On top of that, it is almost impossible for a normal user to learn this is going on. The only mention of «photoanalysisd» is in Activity Monitor. This should not be the only location to learn about something that is using days of CPU time. For a feature I imagine a lot of people either don’t want or don’t care about having on every device with Photos.

Yet it gets worse.

There are seemingly very few ways to actually get it to stop or even pause. Supposedly, it only runs when a) the machine is plugged in and b) Photos isn’t running. This means that people that want it to pause so they can get CPU cycles back resort to running off battery unnecessarily or leaving Photos open for no reason. Even leaving Photos minimized makes it start up again. However, mine still runs even with Photos focused, so I guess it doesn’t really matter.

You can also just let it finish, but this takes quite a long time (well after their 14 day return policy is up). It also seems like it gets stuck for some people, never finishing.

You can use launchctl to disable and kill the service. However, you have to make sure to disable all the appropriate services, otherwise this is only a temporary reprieve.

Exit fullscreen mode

You also should be able to (re)move the service file, but that may or may not affect system stability. Not something I really want to try, personally. YMMV.

How to actually do it

To do this, you’ll need to open up Terminal and run a couple of commands. Any time you’re asked to copy and paste commands into your terminal, it’s a good idea to at least have at least a basic understanding of what the commands are actually doing to your system.

The following commands are really 4 command. The && basically means «run the first one (on the left) and if that’s successful, run the second one (on the right). launchctl is the command that is used to control system services in macOS.

First, you’ll disable and kill the GUI instance:

launchctl disable gui/$UID/com.apple.photoanalysisd && launchctl kill -TERM gui/$UID/com.apple.photoanalysisd

As well as the actual service:

launchctl disable user/$UID/com.apple.photoanalysisd && launchctl kill -TERM user/$UID/com.apple.photoanalysisd

Closing Thoughts

First off, if anybody from the Photos team somehow ends up reading this, I’m begging you to give us an off switch for the People tab. I don’t use it, I don’t plan to use it, and it is a huge waste of resources.

Источник

Question: Q: kill photoanalysisd

It is obvious that the function of Photo photoanalysisd is killing CPU with my 2009 Mac at 50-80% CPU and grinding through my life-time with of photos. I require a kill feature in terminal to stop this process or as a minimum moderate CPU allocation to this application to 10-20%. I also note that in the latest IOS agreements the wording did not say that all my photos would be micro analysed for details so slowing up my CPU by a factor of 10 fold.

Mac Pro, iOS 11.1, 2009

Posted on Nov 10, 2017 11:48 PM

Helpful answers

I tried all of the proposed solutions, in the end the only thing that worked was temporarily moving my photos library to another folder so the daemon couldn’t find it. I only have a couple dozen photos in my library, and this task was KILLING my machine — very unresponsive. 100% CPU on both cores with fan at max RPMs. As soon as I moved the photos library the CPU usage dropped from 100% on both cores to around 5%. Now my machine is usable again (13″ Mid-2010). It is curious that my two newer MacBooks do not have this issue.

Mar 22, 2018 11:50 AM

photoanalysisd should not be running, while you are working with Photos. Are sou seeing it using CPU time, while you are browsing or editing photos?

The safest way to prevent photoanalysisd from running is using Photos — while you are browsing or editing Photos, the process should not be running. And if you are not using Photos unplug the drive with your Photos Library. The process cannot run, if there is no Photos Library on any mounted drive.

You can kill or stop a process from the Terminal using the command launchctl, but killing alone will not suffice, because Photos will just restart the process again. You would have to disable photoanalysisd from ever running again.

into a Terminal window to see the documentation for this command.

This command will disable photoanalysisd:

launchctl disable gui/$UID/com.apple.photoanalysisd

And this will kill the currently running process, after you disabled it.

launchctl kill -TERM gui/$UID/com.apple.photoanalysisd

To enable it again, use

launchctl enable gui/$UID/com.apple.photoanalysisd

But Photos 3.0 is not of much use, if you prevent it from collecting the categories, places, faces. I#d let the process run during the night, to get the task done.

Источник

What is «photoanalysisd» and why is it using 77% of my CPU?

We got a new iMac for Christmas and it has seemed really slow for the past couple of days. In desperation I checked out Activity Monitor and it shows photoanalysisd as the guilty process that is hogging my CPU. I assume this is related to the Photos app, but that’s not even running!

What is «photoanalysisd», why is it using 77% of my CPU, and can I safely stop the process?

8 Answers 8

Your iMac is currently processing the photos in your Photos library, presumably because you’ve just imported/converted an existing Photos library from an earlier version of macOS.

If you suspect this has been the cause of your sluggishness for a couple of days, then it’s most likely you’ve got a very large photo library and that it’s being processed for the first time on your new iMac.

The fact that Photos isn’t running actually fits with your scenario, as launching the Photos app will pause the photoanalysisd daemon.

Although it takes a long time, once it’s finished your Photos app will be able to perform a lot of advanced functions due to all the metadata etc it’s processed, so I would let it finish what it’s doing.

NOTE:

Should you need to pause the process in order to free up some of your CPU, I would recommend just opening the Photos app for a while and then quitting it when you’re not using the computer. Note, however, that minimising the Photos app will act to restart the photoanalysisd daemon, so just leave it running in the background while you want to keep the daemon paused.

Update for 2019, 16″ MacBook Pro running Catalina 10.15.2:

start Photos, let it continue past the first dialogue box;

now Preferences… in the main app menu under Photos just right after Apple logo is clickable (it wasn’t before);

Preferences… ( ⌘+, ) → General tab , and untick both check boxes in Memories;

close Photos.

This stops photoanalysisd cold, no reboot or kill required.

After photoanalysisd had been taking up 3 cores for over a month, I found a solution that reduced the CPU usage dramatically for me on High Sierra. I went into Photos and added names to some pictures — 4 pictures in total using 3 names. Photoanalysisd is currently using 0% whether or not Photos is open.

I have only a dozen or so photos in my library (this is my spare computer, my photos are on my main computer) and I’ve let the process run for a week, and it is still eating up 100% of both cores. My machine is unresponsive with the CPU fan at 100% (13″ MacBook Pro Mid-2010). None of the solutions I found on the web worked, I finally temporarily renamed my photo library to hide it from the deamon, and instantly had both CPUs go from 100% to around 5%.

I don’t use the Photos app and I have no photos in it. Still, my mac (Catalina) is regularly slow and sluggish due to this process. I’ve now renamed the Photos library which seems to help. It’s annoying constantly having a process running for a feature that is not used. Surely Apple can detect wether they actually need to run this process?

/Pictures/Photos Library.photoslibrary directory. I did kill the photoanalysisd process and haven’t rebooted since so I can’t actually say if renaming the folder helped. I’ll do some testing to see if I can reproduce it.

Might I suggest the use of App Tamer?

It lets you pause/stop a process when it reaches a % of the processor time.

Since I use it, my computer temperature is always quite low.

P.S.: I am not affiliated at all with App Tamer. I am just a happy customer!

In my case, it was photolibraryd and not photoanalysisd that was hogging CPU and also causing massive HD churn, but I’d like to provide an answer here that worked for me in stopping photolibraryd, because (1) I think these tips will work for stopping photoanalysisd too, (2) this page is one of the top Google results for people searching for info about photolibraryd, and (3) none of the advice on this page (as of 2021-07-01) worked for me in stopping photolibraryd.

First, I was initially experiencing massive disk churn, particularly disk-writing not reading. This started when I moved the Photos library from one user account to another on the computer. This problem was partially due to the fact that my new account did not own the files inside the Photos Library bundle. I had to open the bundle (go to

/Pictures/Photos Library.photoslibrary and right-click it, then choose «Show Package Contents»), Get Info on each subfolder (database/, external/, originals/, etc.), and under the Sharing & Permissions section add my new user account, set its privileges to «Read & Write», and then click the ellipsis-in-a-circle button at the bottom and choose «Apply to enclosed items…». I had previously given myself Read & Write privileges for the overall Photos Library bundle, but this was not enough.

Giving myself R&W access to all the contents stopped the disk-writing churn and the errors that were showing up in Console.app from photolibraryd, however it still continued to dump tons of non-error messages into Console and was reading continuously from the HD at 15MB/s for hours despite the fact that I don’t have enough photos to occupy it for more than a couple minutes at that speed.

At this point, the advice here from mbackschat on 2020-01-03 worked instead, which is to rename the folder

Источник