Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[scottlf]

On average my MacBook Pro tends to hit somewhere around 160% processor usage when running the latest release of MC 25. I've tried turning off the "check for library updates in the background" and I've also turned off the media server, but it's still awfully high.

I'm running Mojave 10.14.6 on a 2015 MacBook Pro, 28 GHz Intel Core i7.

I've gone back to MC 21 for the meanwhile -- and processor usage is modest, about 1.4% or so.

Any thoughts to what could be eating up processor cycles like this?

[blgentry]

That does seem really high.  The biggest offender for this is typically the spectrum analyzer (the little bouncing bars to left and right of the text display at the top).

On my system, CPU utilization is about 3% with those off, and about 30% with them on.  That's on a 4GHz quad core i7 iMac.

To turn them off, right click on the display area, and in the menu that comes up, deselect spectrum analyzer.

Hopefully that will "fix it".

Brian.

[janpeeters]

That does seem high indeed.
Is any auto import proces running? Or grabbing of images online?
With one spectrum analyzer on I'm on 8 and with one about 3,3%.

[bob]

Also if it's rebuilding thumbnails or re-analyzing the audio for some reason it will use a lot of cpu. The log would be helpful.
It idles around .9%, playing, dual spectrum analyzer enabled, 15%, w/o analyzer 6.3%
Mac mini 2012 w/retina monitor.

[scottlf]

Update: I upgraded it to 25.114 and the processor usage has calmed down -- around 2.0 to 2.5% when playing audio, with the spectrum analyzer off.

[scottlf]

And as of today it is pegging the CPU at 99.8% CPU usage. If I run Media Center 21 it's only a few % maximum.

[scottlf]

One particular part of the log file seems to be doing some sorting: here's an excerpt.

0183672: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.015
0183777: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.015
0183882: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0183985: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0184089: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0184196: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.017
0184304: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0184406: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 3; Elapsed ms: 0.015
0184508: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.015
0184610: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0184716: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.015
0184822: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.015
0184927: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.015
0185033: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0185140: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0185247: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0185351: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0185457: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0185558: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 8; Elapsed ms: 0.018
0185663: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 3; Elapsed ms: 0.016
0185768: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.015
0185874: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0185980: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0186086: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.016
0186191: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 3; Elapsed ms: 0.015
0186296: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.035
0186402: 123145520713728: Database: CMediaInfoArraySort::Sort: Files: 4; Elapsed ms: 0.0

[scottlf]

Then it finished whatever it was doing and processor load went from >100% to almost nothing -- 0.1%, that sort of thing. If I quit and restart, it goes up to high CPU usage again for a while with that same tons of lines of Database: CMediaInfoArraySort::Sort: Files: 19.

Is it attempting to sort my entire database every time it launches? I have a very large library on a server.

[JimH]

25.0.116 is in a thread at the top of this board.

[scottlf]

Update: I updated to 25.121, but most importantly, I did a fresh install after having deleted preferences files.

That seems to have stopped the long and processor-intensive sorting after launching the program, and processor usage has dropped dramatically.

[scottlf]

But when I ran it today it started up with the sorting and the massive processor usage.

I understand that this only lasts for a few minutes -- but it revs up the fans in my computer something fierce, and I can't for the life of me understand why there isn't some way to turn this particular behavior off. It isn't in earlier versions: I've never experienced it before in MC 21. (Which I'm going back to running, since it does what I want without hassles -- which is to play music from my server.)

[JimH]

Just let it run.  MC builds thumbnails and analyzes audio.  Depending on the size of the library, it might take an hour or more.

Under Services in the Tree on the left, look at Reporter to see what is going on.

[blgentry]

My collection is rather small for an MC user:  Less than 10,000 files.

But I've been using MC since version 20 and have not seen this particular behavior.

You said "I have a very large library on a server".

I'm assuming you mean that your music files are on a NAS of some sort.  You have not moved the MC DATABASE files to a NAS have you?  That would potentially lead to poor performance.

Brian.

[scottlf]

My practice is to connect to a MC server as a client. So presumably the MC that runs on the server should be doing all that sorting, right? But it seems that the client is doing the sorting as well and running up the CPU.

However, MC 21 does *not* do this, even though it connects to precisely the same server.