The crazy thing I did to fix Yosemite performance

[Jeremy Huddleston Sequoia]

> On Nov 3, 2014, at 11:37, Jeff Singleton <gvibe06 at gmail.com> wrote:
> 
> OK look...
> 
> I explained myself pretty clearly. I was just sharing what I did and how I did it because that is the right thing to do.

Whoa.  Such hostility.  That is certainly not called for.  I asked for clarification because I did not understand your post.  You may have thought it clear, but it wasn't clear to me which is why I asked for clarification.

> I know what MDS, MDWORKER do...why does everyone think that I don't?

I never assumed anything.

> The issue was after upgrading to Yosemite, those indexing processes would never stop. Sometimes hitting and staying at +100% CPU usage. My fans would be spinning at maximum non-stop even with no Applications launched.

Yes, I understand that.  Did you take a sysdiagnose or mddiagnose?  Did you file a radar?  Was there anything relevant being printed to syslog?  What files were being indexed during the runaway?

> And no...deleting the .Spotlight folder is actually recommended by Apple as a possible step to resolve the run-away CPU issue with mdworker indexing.

It won't *STOP* spotlight from indexing.  It will just reset everything and cause Spotlight to restart.  Possibly that will get Spotlight to behave better the next time, possibly not.  Either way, it is expected that it will be active indexing after you nuke .Spotlight.

> I don't want to explain further on the editing of the .plist files because that is where things made a turn for the worst.
> 
> What solved my performance issues was exactly what I explained in my first email.

You mean just re-installing?  That's not really a good solution.  I'd much prefer figuring out a good solution than recommend that users reinstall whenever they experience an issue.  So back to my original response.  Do you have a sysdiagnose, mddiagnose, fs_usage, syslog output, or anything to go on?



> I guess I wont share anymore...because having to re-explain over and over is more effort than actually backing up, restoring, wiping, and reinstalling.
> 
> On 11/3/14 1:24 PM, Jeremy Huddleston Sequoia wrote:
>> 
>>> On Nov 2, 2014, at 10:06, Jeff Singleton <gvibe06 at gmail.com> wrote:
>>> 
>>> Hi,
>>> 
>>> So after much frustration, much stress, and of course, I broke my Mac in the process. Backed up my user folder from single-user mode (since my mac would not boot all the way). Then I wiped and reinstalled Mavericks, upgraded to Yosemite, and then restored my user folder.
>>> 
>>> Back story: In an attempt to figure out why the services mds and mdworker were running away with my CPU. Nothing I did resolved this, including putting every single folder except /Applications in the exception list for Spotlight.
>> 
>> mds and mdworker are Spotlight.  They run at low priority and will chew up CPU and disk I/O to index your system.  You should expect them to be a bit more active than normal after an OS upgrade.
>> 
>> If you see abnormal behavior, you can run mddiagnose to create a zip file containing logs and other useful information for debugging.  Submit a bug report at http://bugreport.apple.com and include the diagnostics.
>> 
>> 
>>> This is where I started editing LaunchDaemons and LaunchAgents and where breakage occurred.
>>> 
>>> So...
>>> 
>>> This literally resolved all of the performance issues I saw reported from many others besides myself about the performance of Yosemite via the standard upgrade path.
>> 
>> Can you elaborate on "This"?  What do you mean?  What solved your performance issues, and what perf issues were you having?
>> 
>> 
>>> On Nov 2, 2014, at 16:54, Jeff Singleton <gvibe06 at gmail.com> wrote:
>>> 
>>> Trust me.  I tried everything. Resetting the SMC, PRAM, permissions
>> 
>> Which should have nothing to do with the issue.
>> 
>>> , manually deleting the .Spotlight folder from /. Anything I could find on any Apple related blog/forum, I tried it.
>> 
>> Deleting .Spotlight would just keep Spotlight chugging along as it will want to replace the now-missing data.
>> 
>>> Even going so far as to exclude lots of folders from my home Library folder, the same for System Library folder, my external drive, Bootcamp partition...none of it mattered.
>> 
>> Did you take a look at logs to see what it was indexing.  A quick check of fs_usage should tell you what files are being indexed currently.
>> 
>>> The only thing that had any affect was to stop the mdworker services and the syslogd service.
>> 
>> mdworker, yeah.  If you stop it, it won't run.
>> 
>> syslog has nothing to do with it.  It's just logging what it's told to log.  If you see a lot of CPU usage from syslogd, check what is actually being logged as certainly something else is just being very noisy, and that's what you want to look at rather than syslogd.
>> 
>>> That is the only time the CPU usage dropped and the fans started slowing. Of course, right after I rebooted, they started back up again.
>>> 
>>> Somewhere in the middle of all that I probably forgot to revert an edit on one of the plist files and thats when it stopped booting to the GUI. Single-user mode was the only way, which required manually mounting my external drives and copying my user folder to it.
>>> 
>>> Booted to my Mavericks USB installer, completely wiped the main drive, installed Mavericks, and upgraded to Yosemite. Then booted to single-user again, and restored my user home folder.
>> 
>> Seems a tad... excessive...
>> 
>>> From that point, mdworker did its initial indexing, and then dropped down to normal usage. Now the fans only spin up when I am actually doing something like compiling something under MacPorts.
>> 
>> And do you have anything which can be used to try and determine what was actually going on with your system at the time?  Did you take a sysdiagnose or mddiagnose?
>> 
>> --Jeremy
>> 
>> 
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users