Hi, High CPU usage is usually caused by a bloated sync database. I'd suggest replacing it:
* If you haven't done so lately, make a backup of your iCal calendars (iCal File menu, choose "Export...", then choose "iCal Archive...") * Quit out of all open programs * Make sure that nothing is syncing (Spanning Sync, .Mac, iSync) * Move this folder to the trash: ~/Library/Application Support/SyncServices (~ refers to your home directory) * Restart * Open iCal and give it a few minutes to write out the new database Also, the MDS processes are related to Spotlight. Spotlight may be trying to index some of Spanning Sync's data files, causing unnecessary CPU usage after each sync. To prevent this, open the Spotlight pref pane and drag this folder to the list in the Privacy tab: ~/Library/Application Support/Spanning Sync Please let us know if that doesn't address the problem or you have other questions. Thanks, Byron --- Byron Shaheen [email protected] http://spanningsync.com On Aug 3, 12:49 am, J <[email protected]> wrote: > After the most recent update (3.1.1) my CPU utilization skyrocketed. > Whenever iCal i open, CPU utilization shoots up on one core to 80% > (iCalExtension) and other processes shoot up to 50% on the other core > (mds and mdworker). > > I have to do a bunch of killalls to get the system back under > control. But what makes it difficult is that the processes > continually spawn new processes. So mdworker creates a new process > (and kills the old one) every 3-4 seconds. > > Basically, iCal has become completely unusable. Please fix this > issue. I am running SpanningSync 3.1.1 on SnowLeopard. -- You received this message because you are subscribed to the Google Groups "Spanning Sync" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spanningsync?hl=en.
