{"id":5149,"date":"2018-07-09T23:22:59","date_gmt":"2018-07-10T06:22:59","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=5149"},"modified":"2018-07-09T23:22:59","modified_gmt":"2018-07-10T06:22:59","slug":"backup-and-sync-cpu-memory","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/backup-and-sync-cpu-memory\/","title":{"rendered":"Q & A: Why is AlwaysUp Reporting the Wrong CPU and Memory for Backup and Sync?"},"content":{"rendered":"
\"Q<\/div>\n
\n  I am using AlwaysUp for Google Backup and Sync<\/a> as a windows service. My files are syncing but in checking the processes on the server, Backup and Sync is showing 30% CPU usage and 688 MB memory. Yet AlwaysUp in its daily reports quite often shows CPU as 0\/0 and Memory as 2.2\/11. As you can see the average is suspect and the peak is way off. Am I missing something in setting up the daily reports?<\/p>\n

— Oscar Romo, TECHsperience<\/a><\/p>\n<\/div>\n

Hi Oscar. Your configuration is not to blame. That puzzling situation is the result of how Backup and Sync operates. Let me explain.<\/p>\n

Backup and Sync runs in an executable named googledrivesync.exe<\/b>. The Task Manager will show that process running on your server:<\/p>\n

\"googledrivesync.exe<\/a><\/div>\n

But wait — why are there two<\/b> googledrivesync.exe processes??<\/p>\n

If we pull out the big guns (i.e. Microsoft’s excellent Process Explorer<\/a>) to investigate, we see that the first instance of googledrivesync has spawned the second as part of normal operation<\/b>. And furthermore, while the first process is idle, the second\/child process seems to be working pretty hard (its CPU is almost 50%):<\/p>\n

\"googledrivesync.exe<\/a><\/div>\n

This “two-process operation” explains the discrepancy you have noticed. <\/p>\n

When AlwaysUp launches Backup and Sync, it monitors the first googledrivesync.exe process<\/b> that was created. Because that process doesn’t use much CPU or RAM, AlwaysUp will present very modest numbers in its daily and weekly summary reports.<\/p>\n

However, when you check the processes on the server, you are likely looking at the second googledrivesync.exe process<\/b>. That child process seems to be doing the heavy lifting, leading to higher CPU and RAM values in Task Manager.<\/p>\n

The end result is that the CPU & memory measurements in AlwaysUp’s reports may not be very useful when running Backup and Sync as a service. Sorry about that. Rest assured that your files will always be copied though, which is the main job you hired our software to perform. \ud83d\ude42<\/p>\n

Please be sure to get in touch<\/a> if you have any followup questions.<\/p>\n

Happy syncing!<\/p>\n