Extrem slow Save Dialog in Yosemite

[Viking2]

When I use save/save as it takes over a minute to get response

Searched net and found solution:
rm ~/Library/Caches/CloudKit/CloudKitMetadata*;killall cloudd

But it does not work on my computer

How to fix? It is a pain!

 

[Ledgem]

The full solution requires more than just deleting the three files (which your command does); you also need to kill the running process to force the recreation of new ones.

For anyone else having this problem, the full instructions are at http://osxdaily.com/2015/04/17/fix-slow-folder-populating-cloudkit-macosx/

Viking2, if the command worked properly and the files were really deleted, the step you're missing is to open Activity Monitor and quit (or force-quit, to be sure) the process "cloudd". It will reopen immediately after being quit and you'll see that the three files have been regenerated. Browsing in the Finder and bringing up the save dialog should all be back to their usual speeds.

I did this fix a few days ago and it's been working just fine. However, one person replied to the OS X Daily article saying that the problem returned and that they had to do it again. So... keep that link handy, just in case the problem comes back.

 

[Viking2]

The full solution requires more than just deleting the three files (which your command does); you also need to kill the running process to force the recreation of new ones.

For anyone else having this problem, the full instructions are at http://osxdaily.com/2015/04/17/fix-slow-folder-populating-cloudkit-macosx/

Viking2, if the command worked properly and the files were really deleted, the step you're missing is to open Activity Monitor and quit (or force-quit, to be sure) the process "cloudd". It will reopen immediately after being quit and you'll see that the three files have been regenerated. Browsing in the Finder and bringing up the save dialog should all be back to their usual speeds.

I did this fix a few days ago and it's been working just fine. However, one person replied to the OS X Daily article saying that the problem returned and that they had to do it again. So... keep that link handy, just in case the problem comes back.

Thanks, I did that before (forgot to mention it), but it came back after a while. But last time I forgot to kill the Cloudd-process! Did it now and it works as normal now. Still I think it will come back!
Is it a bug in Yosemite?
Stefan

Ps. it came back within an hour

 

[morkus]

Has anyone found a permanent solution to this yet?