Topic : Atsserver and mdworker

Topic Archived This topic has been archived - replies are not allowed.


This question is answered. "Helpful" answers available: 2 . "Solved" answers available: 1 .



            Permlink
            Replies : 24 - Pages : 2 [ 1 2 | Next ] - Last Post : Mar 13, 2008 12:04 PM by: moseley
Codeslave

Posts: 7
Registered: Oct 26, 2007
Atsserver and mdworker
Posted: Oct 26, 2007 6:58 PM
 

Ive had 5 clean installs so far. (whew) However on my c2d 17" mbpro atsserver and mdworker have now been running at ~20-40% cpu for 5 hours. Ive killed them etc etc. I know its usually a font cache problem, But Ive yet to find any font caches in the normal areas. Anyone else having this problem?? Thanks

Codeslave

17" c2d mbp   Mac OS X (10.5)    
P2x

Posts: 6
Registered: Feb 27, 2006
Re: Atsserver and mdworker
Posted: Oct 26, 2007 10:05 PM   in response to: Codeslave
 

Hi. Yep - I've got the same problem.

I did a fresh install on my Mac Pro and then used the migration assistant. I just noticed the problem about 10 minutes ago.

MacBook Pro   Mac OS X (10.4.5)    
P2x

Posts: 6
Registered: Feb 27, 2006
Re: Atsserver and mdworker
Posted: Oct 26, 2007 10:13 PM   in response to: Codeslave
 

mdworker is the spotlight process and is no doubt indexing the new install - although I don't see why or if the ATSServer process should be connected to this?

MacBook Pro - Mac Pro - Mac Mini (G4)   Mac OS X (10.5)    
Codeslave

Posts: 7
Registered: Oct 26, 2007
Re: Atsserver and mdworker
Posted: Oct 27, 2007 4:21 AM   in response to: P2x
 

the two may not be related. I did a clean install aswell and its now been running for 13 hours. disk repair etc are all fine

Many   Mac OS X (10.5)    
maria_m

Posts: 2
From: France
Registered: Oct 27, 2007
Re: Atsserver and mdworker
Posted: Oct 27, 2007 7:13 AM   in response to: Codeslave
 

I think I got it. I wasn't using my admin account, even though my personal account has admin privileges. So I logged into the admin account, and while Spotlight was indexing, mdworker wasn't showing up in the Activity Monitor, and CPU resources were fine. Indexing was done after about an hour and a half, then I logged back into my personal account, and everything seems back to normal.

Macbook C2D   Mac OS X (10.5)    
Codeslave

Posts: 7
Registered: Oct 26, 2007
Re: Atsserver and mdworker
Posted: Oct 27, 2007 7:20 AM   in response to: maria_m
 

I agree I think its totally the amount of data you have on your drive. I have 110gigs on the drive. It JUST finished and all is good. Something like 17 hours

17" c2d mbp - Dual2g g5 - mini - c2d macbook - 20" Imac   Mac OS X (10.5)    
Codeslave

Posts: 7
Registered: Oct 26, 2007
Re: Atsserver and mdworker
Posted: Oct 27, 2007 7:21 AM   in response to: Codeslave
 

Patience if you have tons of data

     
cbd2


Posts: 379
Registered: Feb 19, 2006
Re: Atsserver and mdworker
Posted: Oct 30, 2007 3:31 AM   in response to: Codeslave
 

My MBP (Early 2006) is having a fit with ATSServer - it consumes up to 99% of my processor at times. It can't be Spotlight indexing, unless it takes Spotlight 3 1/2 days to index. Everything is so s-l-o-w with ATSServer consuming so much precious processor time.

There must be a solution... can anyone offer any suggestions or solutions?

MacBook Pro Intel Core Duo, 1 2.16GHz (Early 2006)   Mac OS X (10.4.8)    
cbd2


Posts: 379
Registered: Feb 19, 2006
Re: Atsserver and mdworker
Posted: Oct 30, 2007 4:21 AM   in response to: Codeslave
 

I just got smart and checked Software Update and there is are two updates - "Login & Keychain Update" and "Remote Desktop Client" - one of which seems to solve the problem. There is one other update as well, "Backup", but I suspect "Login & Keychain Update" to be the problem solver.

MacBook Pro Intel Core Duo, 1 2.16GHz (Early 2006)   Mac OS X (10.5)    
cbd2


Posts: 379
Registered: Feb 19, 2006
Re: Atsserver and mdworker
Posted: Oct 31, 2007 1:17 AM   in response to: cbd2
 

cbd2 wrote:
I just got smart and checked Software Update and there is are two updates - "Login & Keychain Update" and "Remote Desktop Client" - one of which seems to solve the problem. There is one other update as well, "Backup", but I suspect "Login & Keychain Update" to be the problem solver.

Reply to myself yet again...

No, those updates didn't really 'fix' the problem at all... just delays it somewhat. Having three apps open and doing nothing the processors were again maxing out at 100% usage each. Just now I'm at 100% and 16% and it's Atsserver and mdworker that are hogging the load. Anyone else find a solution yet?

MacBook Pro Intel Core Duo, 1 2.16GHz (Early 2006)   Mac OS X (10.5)   Intel iMac temporarily mothballed  
whuggy


Posts: 147
Registered: Jun 7, 2006
Re: Atsserver and mdworker
Posted: Oct 31, 2007 6:49 AM   in response to: Codeslave
 

These processes started hogging up the system right after I copied over 200 PDF files from an external drive to my MBP drive. What's actually happening is aside from indexing the PDF files themselves, Spotlight also indexes the file contents.

MacBook Mini C2D   Mac OS X (10.5)    
Aussie-Camper

Posts: 1
From: Perth Australia
Registered: Sep 18, 2007
Re: Atsserver and mdworker
Posted: Nov 2, 2007 3:00 AM   in response to: whuggy
 

Ive just installed OSX 10.5 and have noticed these two files running using a fair bit of CPU.
If I click on Spotlight it does tell me it still have a couple hours to index the external harddrive.
When I unplugged my external harddrive then these files did stop hogging the system

Best Regards
Ray

Mac Book Pro OSX 10.5   Mac OS X (10.5)    
cbd2


Posts: 379
Registered: Feb 19, 2006
Re: Atsserver and mdworker
Posted: Nov 2, 2007 5:55 AM   in response to: whuggy
 

Ah! Therein may lie my problem (!?). On one folder, on one external drive, I have a folder of over 2,000 pdf files which range in page count from as little as 200 to as many as 1,400 pages. I'll try including the 2 250Gb Firewire drives (which I've made 'Private') and only 'privatizing' that one folder. If all indexes over the weekend - fine. If not, it's back to square one.

MacBook Pro Intel Core Duo, 1 2.16GHz (Early 2006)   Mac OS X (10.5)   Intel iMac temporarily mothballed  
pheh

Posts: 43
From: Darknet
Registered: Nov 9, 2007
Re: Atsserver and mdworker
Posted: Nov 9, 2007 9:20 PM   in response to: cbd2
 

Switch what you don't want indexed to private, let it do what it needs to index the rest.

You can alleviate the CPU hogging to a degree by reniceing the process.

renice -n 19 -p pid_of_mdworker
renice -n 19 -p pid_of_ATSServer

Seems like a resource hog to me, but I don't remember if it was any worse with Tiger.

MacBook Pro   Mac OS X (10.5)   2.33 GHz Intel Core 2 Duo 2GB 667 DDR2 SDRAM  
Niert

Posts: 1
From: France
Registered: Nov 11, 2007
Re: Atsserver and mdworker
Posted: Nov 11, 2007 12:53 AM   in response to: Codeslave
 

I've experienced the same problem.
Now it's ok. No more processing.

Macbook Core Duo 2,0 GHz 2 Gb RAM 200 Gb HD   Mac OS X (10.5)