![]() However, kernel_task isn't taking much CPU time - kernel_task was taking about 2% of CPU time. Activity Monitor shows kernel_task as having sent 618 MB and received 8.6 GB (!) over the network and read/written 2.69 GB/2.61 GB to the internal HDD. When I checked the Synology NAS, Time Machine was still logged in as a user. Time Machine, from the icon in the menu bar seemed to think it had finished the backup within a few minutes. As Time Machine started preparing the backup, kernel_task kicked in. I have just now watched, on Activity Monitor, Time Machine do a 156 MB incremental backup. Investigating further, and watching Activity Monitor, this seems to be associated with kernel_task. Some months ago, I don't recall exactly when, I noticed that Time Machine backups, even small incremental backups seemed to be taking a very long time. I do Time Machine backups to a NAS and I use the NAS only for Time Machine backups.Ĭurrently the NAS has 2 x 4 TB HDDs (both less than a year old) set up as a single RAID volume - the useable space on this volume is about 3.7 TB with around 60% (2.22 TB) used, the remainder free. ![]() OK, so I don't know if this is an issue with macOS or Synology NAS but I'll ask here and again in the Synology forums - I have upgraded operating systems on both recently.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |