Atsserver and mdworker

Hi all,

I've encountered the same problem. ATSServer and mdworker are consuming 85% of the CPU. I've made a clean install on my mbp c2d 2,33, and i have copyed only my documents back to the hard drive of the mbp.

If there is not that much information, the solution is just to let theese two processes to work until they have finished whatever they're doing?

For anyone having mdworker consume tons of cpu weeks after leopard install, privatize any folders having piece files. ie. torrents.
mdworker would kick up all the time @90-120% cpu until I exempted the torrent download location folders.
Hope this helps someone. mdworker has since become nonexistent. Or at least not a bother. Still will take about 2-3 min after exemption to calm down.

During my first couple of weeks with Leopard I found the same problem with these two processes. Since my Mac is a portable my external drive is not connected all the time. I discovered that when I dismount the external volumes these processes quiet right down.

Also, as someone else said, make sure that you exclude any volumes (in Spotlight Preferences) that you don't want to index.

One more thing I noticed, when you're adding a large number of small files, especially text, to your indexed volume, these processes go nuts for awhile.

Thanks for the tip about the torrent files! I have been plagued with this mdworker problem for weeks. I set my downloads stack folder and my desktop to private. Then the mdworker cpu resources immediately went to zero.

My ATSServer is running at about 60% and mdworker working at about 25% for days now. This may be because I just put about 16GBs of pdf files onto my mac, and I could understand why it would take a long time to index them, but spotlight says it's going to take another -2147483648 hours to index it and I don't know if I can wait that long.

Same thing here ... suddenly mdworker was hogging the CPU ... and per your tip (thanks!!) I privatized the Time Machine designated drive, and voila, system normal.

Chris

I just stumbled onto this problem with my MacBook Pro. For those of you with VMWare Fusion... exclude your Virtual Machine directory. That cleared it up for me.

Thanks! It worked for me.
(I know this thread is two months old but still)

Thanks BoyHowdyDo, phew!
I was starting to panic there. My MBP took a knock the other day, and I thought I had f..... it up.
Then I realised that I had a ton of unfinished torrents, excluded the files, and bingo.... an instant fix.
Hearing those fans wind down was such a relief:-o