Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.5: A cautionary tale on overloaded Desktops in 10.5' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: A cautionary tale on overloaded Desktops in 10.5
Authored by: Anonymous on Jan 17, '08 07:56:51PM

There are a few really annoying things like this in Leopard - the one that annoyed me post so far is:
I downloaded two fairly large PDF's (A few hundred pages each) on another machine. I transfered them via a USB drive, shoving them somewhere in the Documents folder, closed the laptop lid and went to bed.

The next day, I started the laptop up and started using it. For some reason the CPU usage was about 50-70%. "ATServer" and "mdworker" were using a lot of CPU, and made the laptop around 70*c.
Confused, I started running commands like 'ps auxwww | grep mdworker' to find out what it was doing. Eventually "lsof | grep mdworker" revealed it was indexing the two PDF's I had downloaded.

There was *no* visual feedback these files were being indexed. Nothing in the spotlight (like when the drive is being initially indexed), nothing in System Preferences. Just an increasingly hot and slow laptop..
Since I was actually trying to use the l laptop at the time, I ended up archiving the two PDF's in a .zip, which stops the indexing, and extracted them when the laptop was idle..



[ Reply to This | # ]