Uses huge amount of CPU - 2016 didn't
I installed this because I'm having major issues with 2016. Unfortunately, it uses a huge amount of CPU, causing my computer to run with the fan on at all times. 2016 didn't do this - it hardly uses anything. It's mainly the Scheduler service in 2017 that's the problem. What's the deal with that?
And btw, I'm running a brand new, very fast computer with loads of memory. If it's having that effect on my machine, I can't imagine a more typical one can handle the program.
Is the scheduler running all the time, or just at startup or after waking up? Are you using a non-stop backup?
I can't replicate the issue of the schedule service using CPU. There are some additional services in 2017 (mobile backup services) and I don't use NSB so I stop them and set all 3 to disabled. I do use scheduled backups so leave the scheduler service enabled, but am not having any issues with it.
2017 is doing the same for me causing the CPU to go 100%. The mobile services is causing this issue as displayed in Task Manager.
Mercman, welcome to these user forums.
If you open the Services.msc console, you can stop both of the mobile services for ATIH 2017 if you are not intending to use these - go into the properties for these services and set them to Disabled. You can also stop the Non Stop Backup and Sync services if they are not being used.
Given how new ATIH 2017 still is, I would advise opening a support ticket with Acronis for this issue if it continues plus submit Feedback with an Acronis System Report about the problem - reference this forum thread in the feedback text.
I'm seeing this too, Upgraded in place from 2016.
I have it configured to do an 'Entire PC' backup to USB3 local drive and another 'Entire PC' with steam folders excluded to the cloud, both backups are set to run daily.
I used to be able to let the backup run in the background and still use the system for playing games, now, if the local drive backup is running I see multple 0.5-1 second pauses whenever the game needs to load data from the disk.
At first I thought it was just the old spinning iron HDD getting overwhelmed, but it even occurs with games running from my NMVe SSD boot drive and there's no way that can't keep up.
After a bit more investigation, the CPU is pegged at a constant 100%, and Acronis processes account for about 82% of that. This is an Intel i5 6600k running at 4.4ghz under full boost (which it's being kept at) and a noticable increase in fan noise.
I'm not sure if cloud backups have the same effect, I've certainly only noticed it happening during local backup.
The local backup is set to run as low priority.
The mobile service is running, but doesn't appear to be using any resources, so I don't think it's the issue in my case.
I can't be 100% certain if it started with the 2017 upgrade or if it was since the last update of 2016. The stuttering is certainly new but it feels like the high CPU has been going on a little longer.
This system is just under 3 months old with a fresh install of Windows 10 pro 64 bit and bittlocker drive encryption on the internal drives. The external drive isn't encrypted but the backup itself is. I'd been using 2016 for about a year previously on another, older system (now retired) without seeing these issues.
I'll be submitting a ticket to Acronis as well as this post, but I thought i'd throw out the details in case it helps anyone else troubleshoot.
I would guess it's more your over lock becoming unstable when stressed. During gaming, cpu won't impact as much as your GPU. I'm running my 6600k at 4.2 but not constantly either... It throttles up automatically when needed. Try 4.0 and see if you have the same behavior or not. At least test it to validate without assuming. If not, then boost to 4.2 and try again and work back up to 4.4.
I would guess it's more your over lock becoming unstable when stressed. During gaming, cpu won't impact as much as your GPU. I'm running my 6600k at 4.2 but not constantly either... It throttles up automatically when needed. Try 4.0 and see if you have the same behavior or not. At least test it to validate without assuming. If not, then boost to 4.2 and try again and work back up to 4.4.
Thanks for the suggestion, Ill certainly confirm it, but I doubt that's the issue.
4.4 is pretty 'standard' for Skylake chips, and mine is capable of more than I'm asking of it, I had it stable at 4.6 but the increased fan noise from the extra heat wasn't worth it so I wound it back down. Theres also the fact that with ATI16 it was butter smooth backing up in the background for three months.
Edit: Dropped the CPU and ram right back to stock frequency (3.8ghz boost), timings and voltages. I should clarify that 4.4 was my boost speed before, its usualy at 4.2 like yours (well, 800 at idle) the rest of the time.
While the fan is quieter, its still pegged at 100% and if anything the effect in game is even worse, but it goes away the instant the backup is stopped, resuming shortly after the backup is restarted. The game is streaming its data from the 950 pro.
Interestingly I can also confirm the cloud backup doesn't exhibit the same behaviour. I'm running it now and the cpu is only 45% and thats with GTA V running in the background as well (10%). The game itself is perfectly playable in the foreground.
Edit 2: Just noticed your signature, looks like we have quite similar systems.
I have the same CPU as you. Haven't noticed any issues during backup with the current version. However, you may be onto something with high CPU as mine is pegged out at 95-100% during backup as well. Ran 2 tests with a full backup.... one with performance operation set to "normal" and the other set to "low". In both cases, CPU spiked up. Ran another backup program and CPU stays around 40-50% and takes roughly the same amount of time. Weird thing is I don't notice any issues running other apps at the same time as an Acronis backup - even a couple of VM's. The combined high usage and high overclock pegging for a length of time could be the combo that's doing it. CPU utilization does seem to be at play though.
I'll submit feedback on this and reference this thread. Please do the same. Perhaps some other MVP's can validate the CPU utilizatoin on their systems as well with no OC and OC as well?
OC performance usually boils down to luck of the draw on the particular CPU you get. It's something like the top 5-10% manufactured get the best OC performance. 4.4 is closer to the high end and not the norm. 4.6 "stable" if you can do it, great, but probably far from the norm - even with custom water cooling. I'm using an H100i and temps are decent at 4.4, but got random BSOD's so throtted back to 4.2 and haven't had any issues. Voltage requirements for 4.4 start to get a little insane and I'd prefer to keep the CPU for a few years. I can't justify the need for the higher OC either, but that's just me.
http://www.tomshardware.com/answers/id-2971268/6600k-overclocking-advis…
I was just checking out our system specs - nearly identical. I have the Gaming 3 and you the K3. You have double the NVME HD space and memory though :) I'm using a Corsair 750x PSU and don't have a graphics card as I don't game.
Its easily reproduced (for me) in a game like GTA because of the constant streaming in of world data (particuarly with the view distance pushed out), but It was also happening in Elite Dangerous and World of Warcraft (which despite many graphical tweaks over the years, shouldn't cause choking) whenever new models needed to be loaded in.
Odd that despite seeing the same CPU usage it's not causing stuttering for you. I installed the Samsung NMVe driver for the 950, and the Intel Rapid Storage Technology driver for the SATA drives, can I assume you did the same?
Did you activate any of the power saving features in UEFI? Are you running Legacy mode? Is secure boot enabled? (Yes, No, and yes in my case)
The next step (after reseting all the bios settings to default) I suppose is a clean re-install of ATI, but it's getting late here so that will have to wait.
In terms of the CPU OC I don't want to take this thread too far off topic, I only have a sample size of 1, but the guide I read before I started (which I can't find the link for right now) was where I got the suggestion that 4.4 is 'standard'. I guess I got lucky with mine, I don't remember the exact voltage I got it down to at that speed, 1.3v or possibly a tick lower i think.
Yes on all accounts...
Samsung NVME driver installed, latest IRST driver, UEFI mode, Secure boot is off - didn't mess with power settings in the bios so I'd have to go back in and check.
I'm using the Gigabyte advanced profile easy overclock settings - was too lazy to play with manual voltage settings this go-a-round. I really don't do anything graphics intensive on this machine so that may be why I don't see stutter. I'm just using the embedded graphics of the CPU, but don't do any gaming.
It could be that realtime 3D is more sensitive to this, or even that the fully loaded CPU is stalling the GPU (NVidia 1070).
I did read something about some games on NVidia cards stuttering when a certain power saving mode was on. That's not what this is but I should eliminate any possible similar issues with the 170 chipset.
TBH I don't really think it's my hardware but like you said earlier its better to confirm it than assume. And all these UEFI tweaks are easily reverted by loading a profile.
I wouldn't call you lazy, the manual settings are quite fiddly on my board. I had no luck at all with the EZ OC, (that feature does like to crank the vcore), and the XMP doesn't work for the memory either (my sticks are supposed to be 3200mhz CL18) so I had to set it all by hand.
Oh, and another similarity in our systems, I have a 750w PSU too lol.
Trial and error to find the culprit.
Do you also have th bios set to only the dedicated GPU and not just the first priority. I beleive there is an option for both.
As for the memory XMP profile, I had issues too. What I found to work was to first set the CPU OC and save. After that, boot back into bios and then enable XMP for the memory and save again and then go back in and make other tweaks to the bios. The board did not like it if enabled xmp on the memory and OC at the same time and didn't like the OC if I did the XMP first either.
There are other qwerks with the mobo which makes me think this will be my last gigabyte board as some of the behavior is similar to my last X97 board too. It does not seem to like it if you restore an image from the PCIE NVME drive to a standard SATA SSD and remove the PCIE. It's not the bootability that's the issue, it's that the board actually has to reset the CMOS (reboots the pc automatically 3 times and either ends up in the dual bios or will clear your settings to default). I only get this behavior when removing the NVME drive and then trying to boot from an SSD. Funny thing is that after doing that, I can just pop the NVME back on the board and it boots fine with no issues. It's this behavior that brought my from the x97 board to this one (it got stuck switching between the dual bios and never returned) so I'm hoping the same doesn't occur on this one.
````````````````````````
And now that I think about it. I don't get stutter, but every now and then, the graphics will just kind of freeze for about 2 seconds (but not when Acronis is running). I assumed it was the embedded graphics as the cause, but makes me wonder if there's a bit more too it. It's hard to troubleshoot because it's so random when it occurs and only happens momentarily. I'm sure if I gamed on this, I might notice it more. I'll have to do some graphics stressing to see if I can reprodcue the problem - hopefully it's not a gigabyte issue!
I have the onboard graphics disabled.
After a bit more troubleshooting I can confirm it's not down to ErP or Platform Power management options being activated in the UEFI settings.
One possible culprit is that while the priority is low, the compression ratio is set to high.
Still, it didn't happen prior to ATI 2017, so beyond a clean re-install I'm going to hold off on further troubleshooting until Acronis themselves have investigated, and just delay local backups untill I've finished using the machine for the night.
```````````````````````
The odd thing about the XMP thing, is that If I set the timings manually it runs fine, but if I just pick the XMP option it won't POST. To be fair, I don't think there are any 16gb sticks on the compatibility list, certainly none at 3000+. There is a beta UEFI image on Gigabyte's site that 'improves XMP compatibility but since what I have works, I don't want to flash it untill they move it to a full release.
I did a bit of research that suggested that you start to hit diminishing returns after 2400mhz due to increased latency, so after a bit of tweaking I found I could hit 2400 with a CAS latency of 15 and still leave the voltage at 1.2.
I've not tried anything like restoring to a different disk type. I did find the UEFI setup confusing, and had to make a lot of tweaks to get it the way I wanted (although some of that was down to a GPT/MBR mix up) but this is the first and only UEFI board I've used. My last board was a seven year old Gigabyte X58/i7 920 setup that could probably give this one a run for its money but it had a traditional BIOS
After a break away from home I finally got round to doing a full uninstall, cleanup and re-install of ATI 2017.
I downloaded a fresh copy of the installer and completely deleted the old backup and set up a new one with the same settings:
Entire computer > External disk
Compression - High
Priority - Low
AES 256 Encryption
Validate when complete
Validate monthly
All other settings were left at default.
Initial creation pegged the cpu at 100%. Once it's finished i'll make a few changes to the filesystem and run the incrimental backup and see the effect.
I've been testing a little more myself - compression and priority are set to medium, but same behavior when I set the priority to low too.
I can repeat the same behavior with local backups (internal SSD to internal SSD), but when I backup to the NAS, then utilization is only about 40%. Some of the other MVP's are testing as well and they can't repeat the behavior. Wondering if it is related to our Gigabyte controller somehow. Where are your backups being run to - USB or another internal drive as well?
My local backup is to an external 4gb Seagate drive, connected via USB 3.
I could try setting additional backups from ssd to HDD and vice versa for additional data.
Can't rule the board out at this point, but I'm sure it's the Intel chipset that handles transfers rather than anything Gigabyte selected (at least on the data port I'm using, I don't remember if there are other ports on a third party chip). Is anyone else attempting to reproduce while running skylake/z170?
Yeah, Enchantech does - I'm not sure of his specs off the top of my head, but it's a new build with Z170X board (I want to say Asrock), skylake CPU (not sure if it was 6600K) and a couple of NVME hard drives in RAID 0 . He's not able to reproduce the high CPU though - says it's below 40% most of the time although there is a little bit of variation througout the backup.
One thing I would like to try, but have not felt like doing is pulling my NVME drive from the motherboard socket and put it on a PCIE Adapter and see if that makes any difference at all. How, or why that could make any difference, i have no idea, but perhaps this is where the gigabyte may be stressing the CPU to keep up with the transfer speeds to anything attached to the motherboard - I'm taking a big guess here though.
may be stressing the CPU to keep up with the transfer speeds to anything attached to the motherboard
I was thinking on the same lines actually.
I could try connecting the external drive via USB 2 and see if that has an effect. Additionaly my Wife has a 'Sims and firefox' box downstairs that is currently only running cloud backups, I could try a local backup on that to see if I can reproduce it there.
Hello posters,
Thought I would chime in here seeing how my name was dropped in, glad to do so by the way!
So, as Bobbo mentioned I did some testing on CPU utilization on my machine and could not reporduce the high CPU usage. I have since performed some other tests the results of which I think you might find of interest.
First I will list machine specs here:
MOBO -- ASRock Z170 Extreme7+
CPU - Intel i7 Core 6700k
RAM - G.Skill 32GB (2x16GB) Ripjaws V Series DDR4 PC4-25600 3200MHz. model F4-3200C16D-32GVKCPU
Cooler - Lepa LPWAC240-HF CPU AquaChanger240
PSU - Corsair AX860 Platinum PSU
Drives - Primary OS drive(s) - 2 x Samsung SM951 M.2 NGFF PCIe 3.0 X4 256GB in RAID 0. (OEM Drives)
Secondary drive - Samsung 120GB 850 EVO SSD for data.
Secondary drive - Samsung SM951 M.2 NGFF PCIe 3.0 X4 512GB (OEM Drive)
In testing in which I could not reproduce high CPU usage I ran backup tests from this machine over my network to my FreeNAS Server. CPU utilization averaged 30% or below with momentary occasional spikes up to the 70% range.
I repeated these test using the same data to the internal Samsung 850 EVO 120GB drive and results were similar. These tests were run with all default backup settings in the Windows installed TI 2017 build 5554 application.
Today I decided to complete my testing in this and here is where things get interesting.
I first ran a series of tests of my entire OS drive all partitions. Setup the backup as a non scheduled Custom Full scheme. Removed all excluded items in the Exclusions list found in the list begining with C:\ for all test runs done.
First test was to run the backup to my other M.2 NVMe 512GB drive. I decided to add to the test criteria Performance settings of High Compression and High Priority to see if I could get a 100% CPU utilization factor. At start of backup CPU utilization was low 12% to 17% presumably while creating the snapshot. When the backup started in earnest CPU utilization went immediately to 100% and remained there until very near the completion of the backup. Total size of backup at High Compression ended up at 8.5GB. I did not have any other apps. games, or processes other than Task Manager running at the time of backup. I did not notice any stuttering or pauses in the machine dirung the backup process. Now you need to note here that running a backup from a RAID 0 array of 2 PCIe attached drives to a second PCIe attached drive happens very quickly, total time for the backup to run was a mere 1 minute 33 seconds. So as far as severly stressing the macihine, no way!
I then decided to run validtion on this backup. This process also pegged the CPU at 100% for about 3 seconds of the 14 second total time it took to run it.
Second test ran exactly the same as first test only changed compression and proiority back to default, normal and low respectively. The results of CPU utilization mirrored that of the first test. The only difference was in the total backup process time which with this test run was 50 seconds to complete the backup.
Third test was run to an external WD Passport USB 3.0 drive connected to a USB 3.0 case connector. I again ran this test with compression and priority set to high. CPU utilization a bit different here. After the snapshot and backup went into full swing mode CPU utilization did rise to 100% however, that was short lived. Utilization dropped after several seconds to levels of around 70 to 85%. Of course total backup time incresed as one would expect but still total time to run it came in at 2 minutes 1 second. This indcates top performance of the exteranl drive and the USB 3.0 connection as well.
I will note here that my Mobo has 2 onboard storage controllers, one Intel and one ASMedia. The usage of M.2 PCIe drives attached to dedicated M.2 slots on board (of which there are 3) when used disable corresponding SATA III data ports. Given this port disabling I do not use the third available M.2 slot on the board for the secondary M.2 512GB drive, instead I have that drive attached to an available PCIe X16 slot using an ASUS adapter card. That leaves the 2 corresponding Intel SATA ports available. The ASMedia controller is what I use for attachment of the 850 EVO 120GB drive to which my previous tests were run which DID NOT result in high CPU utilization.
In conclusion it would appear that pushing data through the Intel storage controller on Z170 based boards can/does result in high CPU utilization. It appears that when other controllers are used/mixed in the transfer of data CPU utilization is moderated to a lesser overall impact.
So my advice is that if you are going to backup to an internal drive and want to avoid 100% CPU utilization on these Z170 boards you will need that board to support a secondary storage controller to which the destination drive is attached. Sans that your best bet is the use of an externally attached USB 3.0 drive or that of an NAS device or server.
Hope users find this beneficial!
That makes sense to me.
The only thing that still bothers me with the behavior (since it hasn't really been impacting with other system performance) is that when using another backup product, regardless of destination (another SSD or NVME or NAS or external USB drive), cpu utilization is pretty much the same with each of those tests and tends to stay below 50% with similar completion times to Acronis (a little bit slowerr with the other product, but not my much). It seems like there could still be some programming involved that could tweak the behavior - especially since setting high or low performance still ends up maxing the CPU.
It's no dealbreaker, but something I've submitted feedback on in case it can be looked into and/or fixed.
I agree with that, the app should not max out the CPU and doesn't in cases where other storage controllers are involved. I have not submitted feedback yet but I will as I do think this needs looking into! My purpose here was to show results using a bit different approach then what had been posted already. What I need to do is get my test bench ujpdated so that I can test on that a bit as well. I can add an NVMe drive to it for testing I think and it uses a Z97 chipset. This may be an indicator as to whether or not the chipset version plays a role. If I can find the time, I'll see about that. Time has been an issue for me recently, put in 220 hours last month at my real job, Whew!
...when using another backup product, regardless of destination (another SSD or NVME or NAS or external USB drive), cpu utilization is pretty much the same with each of those tests and tends to stay below 50% with similar completion times to Acronis...
Not to mention that even ATI 2016 didn't exhibit this behaviour either, it's a new change with 2017.
Enchantech, thanks for your research. It would be interesting to know if it can be observed on z97 or another intel board. Could be the controller itself or IRST, I remember reading a post on another forum suggesting there were issues with the 'full' version and windows 10, and that it's better to install the barebones driver but i've not been able to find it.
I will do a bit more investigation myself, but since re-installing the other day the cloud backup is claiming it has to upload the full 960gb again (although the rate it's going up suggests its just checking for changes) and I don't really want to interupt it.
Interesting; most of my systems have a ASMedia SATA controller, either on the motherboard (AsRock intel systems) or add-in cards on my PCs with AMD motherboards. I have done most of my testing on units with AMD motherboards. I have only loaded ATI 2017 on my Intel units in the last few days. I also used my Dell Insperon 7000 for testing, but as it was backing up over wireless (no Ethernet port) it may not get as stressed.
Ian
Did a bit more testing this morning.
SSD to HDD, 100% cpu (with very occasional dips to around 90%), about 260gb expected to take 26 minutes
HDD to SSD, 100% cpu (with more frequent and deeper dips, but still mostly maxed), about 128gb expected to take 46 minutes
SSD to External connected via USB2, negligable CPU usage, and the clock speed hovered around 2ghz.
HDD to USB2 looks same as SSD, could be marginaly higher but that could be variations in background tasks.
USB2 HDD to USB3 HDD - almost no cpu usage at all.
The only other thing I can think of that could be a factor is i'm using one of the two USB 3.1 ports on the motherboard for the external backup, but I don't feel it's likely.
I also discovered that reinstalling ATI 2017 and resuming a cloud backup doesn't preserve the exclusions list. My PC spent the night trying to upload my 300gb steam library until I reminded it I don't want it to.
You could see if there is an updated device driver for the USB3.1 controller; if there is it may solve the problem.
Ian
I have the latest Asmedia driver provided by Gigabyte, although it looks like MSI have a newer one, I'll have to check its the same chip.
That said, I don't think USB is the issue. The only common factor I can see is when the transfer speed is high. I think the problem is with ATI 2017.
Keep in mind that ASMedia makes controllers for USB 3.0 which is what you have obviously and in my case on my ASRock board there is in addition an ASMedia SATA storage controller. In outlining my results I found that backup to an SSD attached to that SATA controller did not max out the CPU
Keep in mind that ASMedia makes controllers for USB 3.0 which is what you have obviously and in my case on my ASRock board there is in addition an ASMedia SATA storage controller. In outlining my results I found that backup to an SSD attached to that SATA controller did not max out the CPU
As far as I can tell, on my board the 6 SATA ports (of which 2 can also be SATA Express) are all connected via the z170 chipset, with no additional controlers. There are 10 usb ports (6x3.0, 4x2.0) that also use the intel chip, with two 3.1 ports via a separate Asmeida chip.
There's also an iTE 'super' I/O chip but I don't think that's involved.
For the sake of completion, I attached the external usb drive to one of the Intel USB 3.0 ports (and created a backup from the SSD) and it maxed the CPU, in the same way It had done with the Asmedia USB 3.1 ports
Your board uses an Intel SATA controller to communicate with the Z170 chipset. Some board like mine host 2 SATA controllers. On boards that support PCIe based boot devices, those devices also use the Intel side of this equation. What I witnessed in my tests was that when I ran backup from the NVMe PCIe drive to the SSD connected to the ASMedia SATA controller connector I did not see the maxed out CPU usage. When backup was run to the USB 3.0 connector, which is also an ASMedia controller, the backup did start out a max CPU usage but quickly dropped to a 70 to 80% level. I did not try USB 3.1 as I do not have a USB 3.1 storage deivce. I guess that you do, mind telling us what that device is?
Your board uses an Intel SATA controller to communicate with the Z170 chipset. Some board like mine host 2 SATA controllers. On boards that support PCIe based boot devices, those devices also use the Intel side of this equation. What I witnessed in my tests was that when I ran backup from the NVMe PCIe drive to the SSD connected to the ASMedia SATA controller connector I did not see the maxed out CPU usage. When backup was run to the USB 3.0 connector, which is also an ASMedia controller, the backup did start out a max CPU usage but quickly dropped to a 70 to 80% level. I did not try USB 3.1 as I do not have a USB 3.1 storage deivce. I guess that you do, mind telling us what that device is?
The external drive I have is only 3.0, its just two of the ports that are 3.1. I use them for the 3.0 drive because they are the easiest to find by touch.
It wasn't until today I realised the 3.1 ports were on a different controller.
This is the board I have http://www.gigabyte.com/products/product-page.aspx?pid=5720#ov
Manual is here http://download.gigabyte.eu/FileList/Manual/mb_manual_ga-z170-gaming-k3…
Edit: Double post
Well I'm certainly glad I've persevered with the local backup despite this issue.
Just today windows decided to have a breakdown and popped up a blue screen on startup. Wouldn't even boot to safe mode. Tried all sorts, (most of which involved having to re-enter the bitlocker recovery key again - that gets really tedious by the 14th time)
Finally convinced it to let me 'refresh' while keeping files, got into windows, established that it wasn't some kind of hardware issue stopping boot, then rebooted to bootable media and recovered the C partition image from 2 days ago.
15 minutes and I was back in business, it was far easier than I expected, really impressed. Just sat typing this while waiting for bitlocker to finish re-encrypting the partition.
That's great, success stories are always welcome here. I have not found the time to test on my Z97 board yet, hopefully soon! Thanks for posting.
I randomly, but regularly, have the mobile services start consuming 42% and 48% of CPU resources respectively.
I have a bog standard MB board and CPU ( no over clocking) 32gig RAM GTX 970
Window 10 64bit
This never happened with 2016 so the only change to the system is TI 2017
Have disabled the two services for now.
Also noticed that the Acronis Managed Machine Service Mini is disabled. I can't recall disabling it. Should that be the case and what does it do?
The Managed Machine Service Mini is used to communicate to the Family Dashboard. If you do not use the Dashboard the service being disabled should not matter.
Since you are experiencing issue with the Mobile services client I would open a support ticket on that. It may be an issue that can be resolved.
Well I raised a support ticket (including a link to this thread), and I feel like I've been given a bit of a brush off.
The first response suggested stopping several services. I was sceptical, but I tried it anyway, and It had no effect (and the scheduler service restarted automaticaly when I started a backup).
While I'm aware that some people have had issues with services running away with themselves while not in use, and that stopping the services might help. My ticket did make it clear my issue was during a backup. Made me feel that it was a scripted response and they didn't really read my ticket.
The next response suggested there were disk errors (with instructions for CHKDISK from 'the google') or that my machine wasn't up to spec, because "Acronis True Image programs cannot take 100% CPU."
I ran checkdisk on all three drives (SSD, HDD, & USB) from both an elevated command prompt (which did finish very quickly) and the GUI (also quick) and no Errors were found on any of them.
I suppose it's possible that something between the particular interactions of TI2017 - Windows 10 - Intel RST drivers - and the Intel silicon is causing errors that make TI get into some sort of loop, but no other kind of usage I've discovered, including transfering multi gb files between drives via explorer, exhibits the same behavior.
I've sent another reply to support telling them I've tried chkdisk and the spec is high enough, we'll see whats suggested next.
I'll be resurrecting my previous X58 system as an upgrade for my wife in the next month or so, it'll be interesting to see how the intel controller on that behaves.
John, I submitted feedback too. I think at least a few of us in this thread (2 MVP's) can produce this behavior with SkyLake processors and 2017 while the backup is actively running to the local Intel controller. I don't remember it being as high with 2016, but really wasn't looking for it either and don't plan to roll back to 2016 to test anytime soon.
Tatou. I also disable both mobile services and nonstop backup services regularly (as I don't ever use them). Other services you can or may wish to stop can include the managed machine mini service (if you don't use dashboard) and Bonjour (network discovery service that helps with NAS detection, but is also commonly installed with printers and/or Apple software like iTunes). Not sure why managed machine mini would be stopped on it's own, but if you're not using the dashboard, you can leave it disabled.
Right, well, this is interesting...
As it happens, I've had a few other little niggles with 2017, and I still had the installer for 2016-6571, so just before you posted, I decided to roll back.
(I never noticed much change going from 16-17 but going back it definitely doesn't feel as well organised)
16 detected existing backups but they all needed re-configuring. The full system backup had to be re-configured to just pick up the two internal disks, since there's no 'entire computer option' and then it didn't want to run it.
So I created a new backup from NMVe > USB.
I'm not currently running an OC, but it still maxed out the processor. I'm still certain it wasn't doing that before, which makes me think something else must be the problem. I usualy run games in a borderless window to aid alt+tabing and a recent windows update broke the taskbar so it always stays on top, wonder what else they broke.
My fingers are alternating between typing and rubbing my temples right now.
It gets better, I uninstalled 2016, ran the cleanup tool and rebooted, and re-installed 2017.
Made a new entire computer>usb backup. It's running now, and it's not maxing the cpu...
It's almost 2am here so i'm going to leave it running and go to bed, not sure what the hell is going on right now.
Edit: I set the new backup with normal compression rather than high, made a couple more test backups, one with high compression and one with normal. High is 100% cpu, Normal is around 40%.
Just to update, I setup my test bench with a Windows 10 Preview build 14393 and all current updates along with a clean install of TI 2017 build 5554. The machine is based on an Intel Z97 chipset. I ran backups to an SSD on sharing the onboard Intel storage controller which showed CPU usage averaged below 50%. I then ran another to an HDD attached to an onboard ASMedia storage controller and saw similar results.
Don't think this proves anything but may be of some interest to others.
Hello all,
We've gathered all available information on the issue with the high CPU consumption in the following article Acronis True Image 2017: High CPU usage by Acronis processes.
Thank you,
All posters to this thread.
It is apparent that the Treu Image 2017 application has been optimized to provide best performance on any given platform/hardware configuration. This is something that the end user is not used to seeing so witnessing your CPU running at 100% can be alarming. Not to worry however, todays CPUs utilize thermal throttling so that if temps reach high levels for extended time periods usage will decrease to allow for sufficient cooling.
I just completed a few file/folder tests to see how such tests would stackup to the full disk tests I ran and posted about earlier in the thread. What I found was that CPU usage never got to 100%. I was able to get a peak of 98% usage but for just a few moments in time. I beleive that the application having the Priority level option available allows the user to specify the level of performance relative to other usage of the system during the run of a backup task that achieves optimum performance. During my test for this posts I also ran an instance of the Speecy app to monitor CPU temps and found that on my system with the Skylake CPU, which runs hot anyway, temps remained in a comfortable range. I will also say that the Speecy app shows all four processor cores at full utilization. This is why the CPU usage can be run up to 100% whereas other applications might not.
Other users may find this high usage bothersome or a degrading aspect in the performance of other applications. As for me I like it! The level of performance achievable is such that backups run quickly enough as to not interfere with other computer usage for me. The best of both worlds in my view.