Elements 15 Organizer: Uses 90% CPU / 80 % RAM of system resources

  • 1
  • Problem
  • Updated 2 years ago
  • (Edited)
I've updated my PSE 14 system to PSE 15. Now PSE has lost most of the tags and tries to rebuild the data again. 
I have face identification active. This tool is incredible ressource consuming. PSE takes in average 85% of the system resources for this tool and is runing now 4 days and has identified less than 25% or the faces google picassa has indentified in 2 hours at the same photo data base of 11000 photo.

This can't be true for a commercial programm! Adobe provide a solution asap! Else you get the software back.
Photo of Vivienne Ahlert

Vivienne Ahlert

  • 4 Posts
  • 0 Reply Likes
  • very fustrated

Posted 2 years ago

  • 1
Photo of Steve Lehman

Steve Lehman

  • 619 Posts
  • 78 Reply Likes
11,000 photos?  Really?  And you wonder why your resources are maxed out?   
Photo of Vivienne Ahlert

Vivienne Ahlert

  • 4 Posts
  • 0 Reply Likes
PSE14 was able to handle this volume without bigger problems. Other products (non Adobe) finished their initial scans within 12 hour and you can work inbetween with your computer. I've usd PSE so many year but this time the organizer is the slowest ever
Photo of Steve Lehman

Steve Lehman

  • 619 Posts
  • 78 Reply Likes
Hello again Vivienne,   

Well, it's a long letter but has lots of information for you.   

I don't use my Organizer because it's bulky, runs longer, hogs memory.  Try to use another system for the face recognition task.  Excuse me from saying I was surprised of seeing 11,000 faces.  It reminded me about a tech support problem I had once that might give you a suggestion:  A customer installed 50,000 fonts at once. The fonts booted up along with his computer and froze the system.  He needed to only install 300-500 fonts or what was needed for the day.  

In a face recognition program, you are using the same amount of memory as a SQL programmed database. It's huge. SQL is used with major search engines such as Google. Serving billions of parts of information may sound like a huge task but remember, that information is stored on millions of servers and workstations throughout the World, and it is segmented. This way the server serves this task in segments. My suggestion is that you break up your database into smaller files to share on other workstations to perform their search on each, thereby segmenting the task.  If on a server, it is overtaxing the memory.  Even with a terabyte of memory the program can crave it all.  The more memory you have, the more it will crave.  A server that operates several workstations will break up its information to several workstation drives so that it shares (segments) its information to spread out its work load.  This way the server will keep operating seamlessly.

Another lesson can be learned from an Enterprise Server which will serve very large corporations such as banks.  An Enterprise like Microsoft's ENT server, (Enterprise NT) is segmented to several banks that share the load.  It is divided into two initial Enterprise servers which serve as a backup system for each other.  Separately located in huge vaults in two States, they ping each other every 30 minutes to make sure the other is still operating.  If one does not, the other takes over its banking duties for the other to keep the ATM's operating and to safeguard bank transactions.  High speed backup's are every hour.  This is why banks cannot be hacked and is also the reason why our Government cannot be hacked (too easily) as it has safe guards to keep out erroneous visitors.  For example, if Russia says they can hack our systems, they are simply a terrorist but ONLY if we react to it.  If our press says we are afraid, the terror is repeated (constantly).  Remember: the game cannot be played unless we have two players, and in our case, one forfeits.  
Make your database segmented to share the load.  Operating 11,000 faces in one database and to allow it to run 24 hours is asking for a breach, also.  Who is monitoring your system during this time?  

Another example:  When I worked at Microsoft in my first job, my job was "backup man" on a mainframe.  My job was mostly to make sure there wasn't a breach or if there was, my system was backed-up to an Enterprise mainframe system.  Nowadays, Microsoft has combined two mainframes into one but it has double security and double backup's.  It has a lot of firewalls and technicians and its guarded 24 hours.  After that I was almost hired to work inside a large bank vault working backup's on a network overnight as an Enterprise server runs continuously.  But, they broke up the system into segments (the opposite of what Microsoft did) and had more backup's in several States).  By doing this, their system didn't bog down banks or freeze up ATM's or stop a teller from working.  If there are not more tellers in your bank, it could be that the more they have, the more their system is overloaded, slows down or freezes.  Banks don't like embarrassment.  

You might suggest to Adobe to make Organizer a separate system or an Add-on.  I think it should be.  It's quite bulky. It's like having a 4th layer in a 3 layer system.  Adobe and Microsoft has a history of making their systems a 3 layer system which craves more memory and feels bulky.  Example: Oracle's database is a 2 layered system, runs faster but makes more mistakes.  Microsoft "borrowed" Oracle's database system (in the 1980's) called it SQL and added a 3rd layer for accuracy.  The 3rd layer made up for a machine language (binary) issue, as a machine language interpreter.  Adobe took a lesson from that with Photoshop and made it bulky.  At Microsoft I was one of the first test engineers for Photoshop-1 to see how we compared to the competition, Adobe, whose technicians are located in Seattle.  I was at Adobe almost each day. Our 3 layer system craved memory and felt bulky like Photoshop.  Photoshop could lose Organizer to drop its 4th layer, making it stand-alone program.  They wouldn't lose any customers.  

And finally, open your task Manager to find other applications that could be robbing memory.  In Task Manager do not cancel "File Explorer" from its task in the background, otherwise your system goes black as it cancels Windows from operating.  Be careful what you do.   

Steve Lehman, MCSE, Seattle   
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1074 Posts
  • 227 Reply Likes
Vivienne, I am not a 'pro' it specialist like Steve, but I can give you some advice about the organizer, good media management practice... and face recognition.
What's very true in Steve's answer is that 11.000 faces is a joke... I understand you have a catalog of 11.000 media files with perhaps a few thousands apparent faces. That's a pretty small catalog for the organizer. It works extremely fast with my I3 and 8 MB RAM, 60.000 items and a few thousands keywords. It has been reported to work well with more than twice that number (without face recognition).
Now, I am very serious about people recognition (not face recognition). That's for my family, my genealogy tasks or the identification of multiple school or wedding group shots. I'll never use any face recognition gadget software. Never. I don't want to waste time.
That implies:
- not trusting any automatic recognition: I have had enough problems to recognize ancestors in old photos.
- not entering totally useless information in the database. I could tell you exactly how many different people names I have in my 60.000 catalogs. They are stored in keywords, captions or notes. Even if I search for a single name only mentioned once in a note, I get the result within seconds. I don't want 95% of visible faces I don't care about to be scanned and stored.
- not bloating the catalog (dramatic for backups, without mentioning networks...=
- not having a lot of background tasks running, slowing my workflow dramatically.

Yes, the old way is to keyword at import time. Or to select import batches and keyword when you have time.

About the catalog:
It uses mainly an sqlite database, like Lightroom.
It also uses additional resources for face recognition and face tagging. Having a look at the catalog folder is very instructive. The implementation changes in every new version, requiring 'conversions'. Those are very heavy background tasks which account for your problem. Those conversions and visual reindexings are very heavy, even with a powerful computer, especially for the first time.

Note: be sure to keep the default value for 'scratch drives' in your preferences. Don't allow more, you might block your computer totally.
Photo of Vivienne Ahlert

Vivienne Ahlert

  • 4 Posts
  • 0 Reply Likes
Thanks Michel, we reviewed the probem with Adobe Service yesterday evening.
They open a task for the next patch release to solve the problem. It was also a problem in the first versions of PSE 13 and 14,

As you mentioned, I have only 130 peoples I'm looking for in a catalogues of approx. 11000 files. Not so huge for digital photography from 2002 - 2016.

The organizer ramp up ressource demand if you switch to the persons table from 5% to 100% and goes down again if you switch to the other views.
So better not view at the persons table untill Adobe has solved the problem
Photo of Edmond J. Skip O'Neill

Edmond J. Skip O'Neill

  • 12 Posts
  • 4 Reply Likes
My PSE 15 Organizer always freezes on Bulk Imports at around 27 %. Then I have to go into Task Manager to close it.Win 10. Organizer 15 is a POS with no support whatsoever from Adobe.