Big Sur slow copying files

I made the error to install Big Sur (11.1) on an iMac (Retina 5k, 27-inch, Late 2015; 2.2 GHz quad-core i5, 16 GB RAM).

I realized that copying files has become extremely slow. Especially when copying from a disk image mounted on the desktop (but also copying to an external hard drive, or to a NAS). It may take several minutes to sloooowly copy even small files (few MB).

I switched off back up automatically in time machine (will this avoid snapshots?), I added the main HD (2.12 TB fusion drive, > 200 GB free) to spotlight privacy tab to avoid indexing... No cleaner or antivirus apps running not even in background... Activity monitor does not show anything taking CPU resources (WindowServer around 10-15; activity monitor 4.7, kernel_task 3,7), nothing weird showing up in system.log in console (beside some com.apple.xpc.launchd[1] showing service exited due to SIGKILL, and some Coalition Cache Hit).

I also tried to reset SMC, to clean all caches and other vodoos, but no help. I am running out of options. May it be that a 2015 iMac is way too old to support Big Sur?

Thanks for any hint or suggestion!


Posted on Jan 11, 2021 3:11 PM

Reply

Similar questions

10 replies

Jan 13, 2021 2:08 PM in response to donazipe

Hi donazipe,


Thanks for coming out through Apple Support Communities for help with your iMac and Big Sur. It's important your computer remains quick and responsive, so we'd love to help!


Since you mentioned that you've removed the main hard drive from Spotlight to prevent indexing, we may recommend adding it back to rebuild the Spotlight index on your Mac, which would speed up searches and may resolve unexpected behavior.


The following guide has more information to help with rebuilding the Spotlight index. Let us know if this guide helps:


Rebuild the Spotlight index on your Mac


We'd also like to share a great resource with further troubleshooting steps to increase the responsiveness of your Mac:


If your Mac runs slowly


We're here for you if you've got any questions.


Have a great day!

Jan 14, 2021 12:54 PM in response to Leanne_68

Thanks for the suggestion but... with Spotlight indexing on on the main drive, the situation is even worse, and console, system.log, is full of this:

Jan 14 21:50:56 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0600-0000-0000-000000000000[55295]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:50:59 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0300-0000-0000-000000000000[55310]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:33 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0C000000-0200-0000-0000-000000000000[55322]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:33 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0E000000-0300-0000-0000-000000000000[55321]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:34 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0500-0000-0000-000000000000[55323]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:34 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.03000000-0100-0000-0000-000000000000[55325]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:34 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0100-0000-0000-000000000000[55326]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:38 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.09000000-0600-0000-0000-000000000000[55222]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:43 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0A000000-0600-0000-0000-000000000000[55319]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:44 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.07000000-0400-0000-0000-000000000000[55324]): Service exited due to SIGKILL | sent by mds[104]

Jan 14 21:51:44 DZ-iMac-i5 com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0700-0000-0000-000000000000[55320]): Service exited due to SIGKILL | sent by mds[104]

Jan 14, 2021 4:29 PM in response to donazipe

Hi donazipe,


Thanks for the information. As this information you're seeing may not be unexpected behavior, and it may take some time for the Spotlight index to rebuild, you may want to continue to allow the process time to complete and monitor for a significant change.


In the meantime, we can also recommend the steps in the following guide to ensure there is no adware or malware on your computer that may be affecting performance:


Protect your Mac from malware


If you should continue to experience issues, and have completed the steps in the guide provided earlier, reach out to Apple Support directly at that point to investigate further.


Here's a direct link to reach out:


Get Support


Take care!

Jan 21, 2021 4:09 PM in response to Jeff_W.

I've been having the same issue since installing Big Sur. It's painful. I spent almost an hour last night with Apple Support deleting caches, doing disk first aid and more. I have a 2017 iMac Retina 5K, 27-inch 3.8 GHz Quad-Core i5 8GB RAM. I had no issue before installing Big Sur.

I can't drag/drop files at the Finder level without getting spinning wheels and necessitating a Finder relaunch. Adobe CC hangs up constantly even though I've reinstalled. And, now even Keynote just stops working and says it needs help at the Finder level.

This sucks.

Feb 13, 2021 12:12 PM in response to Leanne_68

I have gone through the various options described in the "If your Mac runs slowly" page of the User Guide. I have also checked hardware — disks, cables, ports, etc. — and have zapped the NVRAM and reset the SMC.


After checking everything (more than once), copying files to external hard drives still takes 2 or 3 times as long as it did under Catalina. For example, copying about 1,000 ARW image files took almost one hour whereas the same procedure on the same hardware used to take about 20 minutes with Catalina.


The important point is that exactly the same hardware performs far more slowly under Big Sur.

Mar 2, 2021 5:03 PM in response to donazipe

I am having the same trouble. A 300MB file might take up to 6 minutes to copy. It's annoying. I just bought a brand new MacBook Pro, and it's hanging up more than my 2014 iMac Pro was. Although, I had not yet done the most recent Big Sur update on that one. But it was running Big Sur. It's quite frustrating to have a brand new computer run slower than my old one. Any fixes out there? BTW - I am not a person who wants to get in there and start messing with the OS to make it function normally. When I try that kind of thing, it usually breaks something else. PLEASE HELP! I appreciate anything anyone can offer. :)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Big Sur slow copying files

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.