36 Comments

  1. Playersons

    I have a 10.7 (build 11A511) and found the directory to be excluded from Spotlight to be /Library/backblaze.
    Nonetheless, your solution worked fine, thanks for that.

  2. Playersons

    I have a 10.7 (build 11A511) and found the directory to be excluded from Spotlight to be /Library/backblaze.
    Nonetheless, your solution worked fine, thanks for that.

  3. Zwamkat

    I concur. (Mac OS X Lion 10.7 (11A511)) The directory should be /Library/Backblaze  (Mind the capitals, paths are case sensitive!)

  4. Zwamkat

    I concur. (Mac OS X Lion 10.7 (11A511)) The directory should be /Library/Backblaze  (Mind the capitals, paths are case sensitive!)

  5. Timm

    THANK YOU! I was looking for a workaround for weeks and within seconds this did the trick for me! CPU back, battery life back, cheers!!

  6. Timm

    THANK YOU! I was looking for a workaround for weeks and within seconds this did the trick for me! CPU back, battery life back, cheers!!

  7. JeffA

    More generically if you suspect file changes are causing mdsworker to use a lot of cpu run the following command line commands to see what:

    sudo dtrace -n ’syscall::open*:entry { printf(„%s %s“,execname,copyinstr(arg0)); } | grep mdsworkerThis should show the files being opened in real-time.  Once you get a handle on the files/directories it’s pretty simple to exclude.Apple should provide an easy way to do this from within preferences since so many people have this problem.

  8. Jason

    Thank you, thank you, thank you!!! I could not pin this down. I turned off Spotlight indexing for a while but, that caused all kinds of issues of course… My machine is now running normally again thank God.

  9. troels

    This helped me solve the problem by adding the ~/.dropbox temporary folder for the Dropbox file sync service to the Spotlight Privacy list. Thanks!

  10. armand

    i am in mountain lion, and i use new version of backblaze! i did not find /Liberary/Backblaze but i adde /Liberary/Backblaze.bzpkg but cpu still is running wild! please help me!

  11. geekG

    Thank you for sharing!

    The magic mouse was lagging and i suspected some network intrusion.. but after investigating, ‚mdworker‘ was showing super high on cpu usage.

    I use NAS for timemachine backup, and i suppose when you enter in time machine, it open a folder which is shown in finder [which can be ejected]. So after ejecting that remote-folder from the finder. The ‚mdworker‘ went from high to low.

Kommentar verfassen

Diese Website verwendet Akismet, um Spam zu reduzieren. Erfahre mehr darüber, wie deine Kommentardaten verarbeitet werden.