none
CPU Usage 100% all the time - is this normal? RRS feed

  • Question

  • I've noticed in the task manager that the CPU usage is 90-100% all the time even if no one is using the server. Also the process DEMigrator.exe is using the CPU the most.

    Is this normal?

    What is DEMigrator.exe doing?

    Thanks.

    Tuesday, February 20, 2007 2:01 AM

Answers

  • DEMigrator is indeed service of Drive Extender. It lazily moves files betwen disks, to achive duplication, balancing, etc. DEMigrator is throttled by CPU usage and will step back if any other program uses signigficant amount of CPU power. In other words, it will not cause slowdown to anybody - it gives way to other programs (it uses priority below normal).

    So you should not  be afraid of it. From other point of view, we understand that it causes unnecessary questions, and will work to make it less visible in next versions. 

    Tuesday, February 20, 2007 2:58 AM

All replies

  • No the CPU usage is not normal. My guess is that DEMigrator.exe has to do with Drive Extender.
    Tuesday, February 20, 2007 2:07 AM
    Moderator
  • DEMigrator is indeed service of Drive Extender. It lazily moves files betwen disks, to achive duplication, balancing, etc. DEMigrator is throttled by CPU usage and will step back if any other program uses signigficant amount of CPU power. In other words, it will not cause slowdown to anybody - it gives way to other programs (it uses priority below normal).

    So you should not  be afraid of it. From other point of view, we understand that it causes unnecessary questions, and will work to make it less visible in next versions. 

    Tuesday, February 20, 2007 2:58 AM
  • thanks for your help Sasha.

    do you know if it ever ends lol?

    Thanks again.

    Tuesday, February 20, 2007 3:06 AM
  • Hi,

    I have the same problem...

    And it definately slows down my system.

    Can i stop this service or is it requiered?

    Thanks

    Wednesday, February 21, 2007 5:23 PM
  • I noticed high utilization at a couple different points but it seems to die off after a while.  It could be that there's a lot of work for it to do if you just recently added a bunch of new content to a share that is marked for duplication
    Wednesday, February 21, 2007 5:45 PM
  • My server has been running at 100% since Saturday.  I believe the drives have held up well, and the CPU cooler certainly has, but I came home from work tonight to find a strange smell in the room.  My wife thought it was oil, but it was the beginnings of a PSU failure.  I figured I'd handle it after dinner, and went to organise that.  Came back later to find smoke in the living room, over in the corner where the server lives.  I pulled it out just as a small jet of flame erupted from the back, so I pulled the power and let it cool down.

    To cut a long story short, it seems that the server was running too hot and for too long, and my PSU is now dead.  I've ordered another one which will be here on Friday.  I'm going to 700W this time, to support increasing my RAID array by another drive, and a hotter than usual CPU load.  But no WHS for me for a while

    Dear lovely people at Microsoft, thanks for the opportunity to beta test what is going to be a great product.  In a long history of beta testing and developing stuff, I have NEVER had hardware physically damaged by software before.  Now THAT's what I call fun!!!  Do you think we could have another build soon... maybe one with DEMigrator throttled a little?

    • Proposed as answer by Sunny77 Saturday, August 8, 2009 11:06 AM
    Wednesday, February 21, 2007 8:14 PM
  • wow, how much hardware do you have in that box?  I plugged my old test tower into a kill-a-watt and it was only pulling 58 watts (PIII 1ghz, 2x 80gb drives, 512mb RDRAM).
    Wednesday, February 21, 2007 9:51 PM
  • I have an old Celeron on an eMachines moherboard with gfx included.  Two DIMMs, a DVD-ROM, a couple of cooling fans, one expansion card (the raid controller) and five WD-3200 RAID edition drives.  It had an Antec 450W PSU in it, but that's going to be replaced with a 600W model on Friday.  I guess I hadn't figured on it pulling soo much juice for such a long time.
    Wednesday, February 21, 2007 10:27 PM
  • What could it possibly be doing if there have been no files added to the server recently? Shouldn't it reach a point where the drives are "balanced and stable" and just shut down until files are added or the environment changes (such as a new HD being added or removed).

    Regards,

    Charles

    Thursday, February 22, 2007 7:35 PM
  • Looking at task manager DEMigrator has a priority of Normal - and it kills any user interaction with the WHS desktop.
    Wednesday, February 28, 2007 1:13 AM
  • This occured on my machine also now, DEMigrator running with 100% cpu for 2 hours making everything slow

    I have only one disk in the server right now

    Wednesday, February 28, 2007 11:57 PM
  • I have the same problem with my server. It made it almost impossible to connect to the console and when I did the backup data was not visible. Has anything been done about this?
    Thursday, March 1, 2007 12:49 AM
  • So my Home Server is now in this state as well 100% CPU constantly.  I read this whole thread and no-one suggested what we should do about this -- lower the prio, kill the process, registry change?

    Couple of data points:

    1) I can't lower the priority -- not allowed.

    2) Read Byets and Write Bytes are static so it is spinning just the CPU right now ...

    Can someone please suggest a work around?

    Thursday, March 1, 2007 7:51 PM
  • i'm having the same problem, but at least mine hovers around 70%
    Thursday, March 1, 2007 8:47 PM
  • When the cpu usage is staying between 90% and 100%, is there disk activity?

    Is it possible to run diskmon or filemon while this is happening?

    Thursday, March 1, 2007 8:53 PM
  • The behavior I've seen on my system with basic perfmon counters is that the system will be high CPU for a while and then high disk queue.  It alternates back and forth.  I suspect CPU would be pegged more often if my disk subsystem was faster (I'm running a mix of old IDE and USB drives).  As it is, the processor gets a break every so often waiting for the disks to complete their activity.

     

    Thursday, March 1, 2007 9:25 PM
  • Mine has no READ IO and no WRITE IO but some Other IO.  Just 90%+ CPU -- suspect TaskMGR is the only other process getting a look in.

    I have let this run for THREE DAYS NOW at over 90% CPU --no content or recent backup run -- it is spinning and bnt doing anything useful.

    I have to repeat, the system is unusable and Home Server console takes over five minutes to display and is unusable - unresponsive

    Only option is to kill the process ... 

    Is the throttle adjustable?

    Saturday, March 3, 2007 10:45 AM
  • David, I would do two things:

    First, there's a bug report for what I think is this same issue on Connect. What I would do is use the TalQ tool on the server to upload a log, then vote on that bug report and note in your comments the CAB number of your uploaded log.

    Then, I would try rebooting the WHS. I don't think there's any mechanism exposed for us to adjust the throttling on that process, and it certainly sounds like it's hung.
    Saturday, March 3, 2007 1:45 PM
    Moderator
  • thx guys ! After reading this, ill find nice info about this probl. !
    Saturday, March 3, 2007 4:05 PM
  • Submitted a TALQ. Rebboting make no difference on my system - it just starts up again.

    Main thing it kills is any kind of network activity so my home VoIP system whihc attaches to the server is useless.

    Saturday, March 3, 2007 4:57 PM
  • Ditto.  DEMigrator has held my CPU usage at 95-100% for a few days now, and it's very difficult to login to the server.  In addition, file access from the clients appears to be quite negatively affected.  Is there a registry setting of some sort that will lower the priority for us???
    Saturday, March 17, 2007 2:15 AM
  • I'm running hardware raid 5, so to the system it looks like just one drive. I don't have folder duplication on for any folders since the system is raided. So I don't know is someone should do this, but since I don't need folder duplication, I figured I don't need demigrator.exe to lazily move any files around so I disabled the service, and I haven't had any problems since.
    Monday, March 19, 2007 2:59 PM
  • I'm also having trouble with 90-100% cpu on an amd 64 3200+ machine with 1GB of ram. REgardless of whether I just reboot a machine or leave it running the process sits there continuously.

     

    Although it's not interfering with the whs operation as far as I can tell , it does interfere with the cool'n'quiet operation of the AMD processor. Since the cpu is always busy the processor never gets clocked down or the voltage reduced so the machine runs at full power continuously even though it's running "background tasks".

     

    It's vital for myself at least, that I can somehow get demigrator to let go of the cpu so it can throttle down. I'm fighting a texas climate and Air con power consumption so really would like this box to be able to throttle back since it's active only a fraction of the day.

     

    Any one found tips on how to get demigrator to back off? Restarting the machine doesn't seem to fix the cpu load. Is it safe to kill off the service ? why is the cpu so high when no file copies are happening etc to need moving around or duplicating?

     

    thanks

     

    Sunday, April 1, 2007 6:10 AM
  • Folks, the Drive Extender Migrator Service (DEMigrator) in Beta 2 is a bit of a CPU hog. It just is. Call it a bug if you want because it will be "fixed" in the next release you see (soon, I promise, soon!).

     

    Basically, the algortihm the migrator uses to check for new files to migrate in Beta 2 is purely based on it scanning the namespace looking for new files to migrate.  It should have been smarter, and used file system notifications and other mechanisms to figure this out. It also was programmed to be a bit to aggressive (it was optimized for ensuring files got duplicated as quickly as possible). 

     

    And for what it's worth, it runs at a low CPU priority, so the fact that it's sucking CPU up the whole time doesn't really impact overall system performance (but that's no help to those of you who are worried about power consumption). 

     

    So when we get you an updated release (soon, real soon!) please see how it behaves and let us know if we've nailed it for you or not...

     

    Sunday, April 1, 2007 6:22 PM
    Moderator
  • Oh, thanx a lot! I'm waiting with impatience))
    But only one thing, I have to notice. You told that it
    doesn't really impact overall system performance: this is not right! For example, I've installed a ftp-server (Serv-U, for ex.) to check connection speed (it's real speed is 1Gbit) and tried to download few test files: the speed was about 6mb/s... in comparison with original Win 2003 server's 17-22 mb/s it seems TOO slow!
    And then I looked to task manager, I saw that, of course, ftp-server had the biggest amount of CPU time, but it was only about 50-55%, and all the rest CPU time was gathered by DEmigrator!

    Wednesday, April 4, 2007 7:10 AM
  •  Sasha Dadiomov wrote:

    DEMigrator is indeed service of Drive Extender. It lazily moves files betwen disks, to achive duplication, balancing, etc. DEMigrator is throttled by CPU usage and will step back if any other program uses signigficant amount of CPU power. In other words, it will not cause slowdown to anybody - it gives way to other programs (it uses priority below normal).

    So you should not  be afraid of it. From other point of view, we understand that it causes unnecessary questions, and will work to make it less visible in next versions. 

    Sasha,

    The current version (beta 2) does cause slow down.

     

    When I first installed WHS it (DEMigrator.exe) behaved as I expected, in that it would run at 100% for a few minutes after I put data on the WHS (either shared folders or backups) then return to 0% for the rest of the day. At about 7 days it started running at 100% for an hour or two or more. Then it will oscillate 2 seconds at 0%, 5 seconds at 100%, 2 seconds at 0%, 5 seconds at 100% after half an hour or so it returns to 0%. It seems to be related to connecting a computer to the WHS, but I’m not certain. As I better identify what its doing I plan on filing a bug on it…

     

    Jay

    Wednesday, April 4, 2007 4:50 PM
  • If you enable file handle reads/writes do you see the demigrator task thrashing the file io? That might explain a low cpu but still a reduced ftp throughput.

     

    Just a thought. The CPU priority usually isn't sufficient as a resource control when the process is disk intensive.

    Wednesday, April 4, 2007 8:22 PM
  • DEMigrator on my machine is running at a constant 90-100% CPU and does indeed impact system performance.

     

    I was giving a demo of WHS to a user group the other night and it took 3-5 minutes for the management console to start. I switched to the server desktop and killed the DEMigrater service and the console starts in a few seconds, of course the service restarted itself . . .

     

    Friday, April 6, 2007 11:27 AM
  • I've had good luck speeding up my machine by shutting down demigrator.exe using the taskmanager.  When it comes back up (and it does) , it either doesn't do a whole lot anymore, or it does its job a lot less aggressively.


    Tuesday, April 10, 2007 9:17 AM
  • Well, I would like to reply on this post. Actually Demigrator is the service that is not working exactly as described here since it also starts and utilize a 100% of CPU time even without additional drives in the server machine.

     

    I installed WHS normally and for the next couple of days after the installation, it was working quite fine as described.

     

    Than, I wanted to test adding an additional HDD to the system. It was quite smooth as I accepted. Than I realized for the first time DEmigrator unusal activity. after a couple a days of testing, I tried to remove additional drive - and problems started: server was stucked for hours trying to remove additional drive unsuccesfully, giving me a message that there are no enough space on the drive to move data from extended drive. That was not quite a thruth, since first drive is 160GB SATA HDD and extended drive was only 20GB hdd. On main 160GB drive - there were more than 50% of free space at that time. After 2 or 3 atttempts I removed additional drive, and WHS did all checkups and the rest but the DEmigrator continue to makes me a trouble sluggishing my server to incredible value. It is almost impossible to do any other service or even a remote console while DEmigrator is running at 95-100% of CPU time.

     

    If course I tried to stop the service with TaskManager. When I stoped DEmigrator- after a very short period - server come back to normal operation. I didn't see any consequences of forcefully stopping DEmigrator, - scheduled backups works correctly, all other services are running correctly. Unfortunately, after some time DEmigrator automatically starts again- making my server completely unusefull - while I am on my job- I cannot connect to my home server or ftp server, all other services are almost stopped.

     

    DEmigrator as disk extender function do not have anything to do if you do not have additional disks as you say - but in practice- it continue to utilize 98% of CPU time sluggishing all other services. Not to mention next summer with high temperatures - beta testers should do additional steps in cooling down their server to prevent this "CPU burn-in test" to completely burn out their CPUs. I am close to idea to uninstall completely WHS and to come back to good and trusty Server 2003.....

     

    Best regards

    Wednesday, April 11, 2007 11:06 AM
  • cek,

     

    This is a problem for me too. DEMigrator.exe has been running for over 13 hrs at 90% ish. My WHS box is running quite warm and noisy. I am concerned by both noise and temerpature. I have just taken the side off my case to let it cool a bit. I have my WHS box in hte attic above our bedroom. The noise is almost enough to keep me awake. Luckily my wife is away at the moment so she hasn't noticed it!

     

    BTW, you say it runs at low priority. Mine is set to Normal according to Task Manager.

     

    Any idea how long 'till the next update? Are we talking days, weeks ...? Will this be via Automatic Updates or will it need a re-install?

     

    Othar than this issue, I am really please with WHS. Can't wait for the first release.

     

    Cheers

     

    Ben

    Thursday, April 12, 2007 6:48 PM
  • Ben, if there's a "next update", it will certainly require a reinstall. It should be possible to do a reinstall without losing everything you've stored on your WHS if you have fairly simple hardware. If you have a more complex environment (especially a mass storage device that requires a separate driver to be installed, like a RAID card) you may be better off installing from scratch again.

    Even a reinstall will likely lose server settings and user accounts.
    Thursday, April 12, 2007 8:19 PM
    Moderator
  • OK. So now I have installed the CTP version of WHS. Now, DEMigrator.exe is averaging about 60% CPU utilization when it is running.

     

    This is still too high in my opinion. What is it doing and why does it run for such long periods of time?

     

    Ben

    Friday, April 20, 2007 10:24 AM
  • Well, CTP version came and I installed it instead of beta2 version on a 250GB Sata disk. No additional HDDs for this time - I just wanted to check how DEMigrator works - when there are no additional disks, or without once instaled and later on removed additional disks.

    CTP version, - a week after installation works perfectly - so far. DEmigator present in Task Manager  (on Beta2 version I had to shut down DEmigrator from Task manager) uses up to 5-6 % of CPU time  in a short bursts, than drops to 0%. So far, the server is operating smoothly and silently on my home network consiting of a 3 desktop, PC, a notebook and WHS.

    Remote access to shared folders, WHS Console or home computers works perfectly, FTP server functions quite good with user friendly interface.

    I didn't check yet - adding of additional drives and DEmigrator CPU usage when folder dupliacte is activated. I am little bit affraid that DEmigrator will start again with its abnormal behaviour . I will carry on with this later, after I test other functions. But - 60% CPU utilization as Ben says - is still to high if it remains in the final version. It will slow down WHS which can be used also as the application, game, web or mail server.

    Typical application, which many users will setup on their WHSs is a game server hosting some multiplayer games over LAN or Internet. Using WHS for additional applications presumes that DEmigrator CPU utilization should be kept at the lowest possible level. I setup recently an internet multiplayer game server on my WHS - and with this CPT release and almost inactive DEmigrator - it hosts now the Internet multiplayer game server and TeamSpeak server nicely and smoothly.

    All in one, I am quite satisfied so far, and all congratulations to WHS team for their work. I expect that WHS capable to hande up to10 desktop PCs will for sure have a quite a certain market among PC fans.

    Slobodan

    Tuesday, April 24, 2007 12:36 PM
  •  

    I experienced the same issue with demigrator.exe using 100% CPU.

    When I checked the log-files for demigrator (C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\deutil*.log) all files where approximately 3 GB. When I opened them, i discovered that one file was failing all the time.

    The error message repeating over and over again in the logfiles was this:

    [01.07.2008 11:00:00  c88] OpenedFile:Surprisepen: Error 183 opening {7311C865-EE29-4C16-B9DD-2E9427D6839E},\DE\shares\Users\roger\backup2\mp3\Lydbøker\Radioteater\Lystad & Mjøen - I Syses Tid\10-LYS~1.MP3

    When I checked further I revealed that the file that was failing had the same long file name as the short (Dos 8.3) file name as another file in the folder. Once I removed this file and restarted the Drive Extender Migrator Service the demigrator continued processing and making duplicates as it should. 12% CPU usage and 2B MB/s of disk traffic on both SATA hard-drives in the server.

     

    Tuesday, July 1, 2008 8:24 PM
  •  

    How can I bring it down to about 60 to 80?
    Thursday, July 10, 2008 3:52 PM
  • On another forum they did post a fix for this :
    1. Post a bug report to Connect
    2. Wait a couple of days
    3. When a rep contacts you, download and install 1776, your cpu usage will fall to 15 to 20%

    Ben

    1776,PP!:

    • Disk removal has been improved to handle more edge cases.
    • Last Balanced time in the home server console is now accurate.
    • Migration pass used to never resume after a failed hard drive removal.
    • Migration pass used to get into an infinite loop if a file with a short file name overwrote an existing one.
    • Excessive file notifications caused high cpu load.
    • Server restore through DVD is now faster.
    • Blank regkey for TV recording excludes all files on all volumes
    • Improved stability of backup cleanups
    • Backup fails on initial backup of large volume
    • Tray Notification that informs user of new Connector for upgrade between QFE1->PP1 has changed.
    • Client Upgrade no longer needs the WHS Console to be closed for upgrade to go through.

    Thursday, July 10, 2008 8:20 PM
  • I did that and it took less than 24h to get 1776, now my machin is running fine.

    Friday, July 11, 2008 11:16 AM
  • I run at about 10-15 % and have not noticed a problem with excessive CPU usage.

     

    Monday, July 14, 2008 2:46 AM
  • As I look at my system, I am not even running the DEMigrator.exe process.  Is this because I do not have duplication set up on any of my shares?  If this is a problem people are experiencing, I will stay away from folder duplication.

     

    Monday, July 14, 2008 2:52 AM
  • benogil said:

    On another forum they did post a fix for this :
    1. Post a bug report to Connect
    2. Wait a couple of days
    3. When a rep contacts you, download and install 1776, your cpu usage will fall to 15 to 20%

    Ben


     Hi,
    I do understand point 2 but I don't know what should I do with point 1 and 3. Please be little bit more descriptive for dummies... Thank you
    Thursday, November 20, 2008 6:07 AM
  • Does anybody have any info what Err 170 in the Demigrator log could mean? Or any pointer to list of demigrator error codes wuth description? Thank you
    Thursday, November 20, 2008 6:50 AM
  • RastoJ said:

    benogil said:

    On another forum they did post a fix for this :
    1. Post a bug report to Connect
    2. Wait a couple of days
    3. When a rep contacts you, download and install 1776, your cpu usage will fall to 15 to 20%

    I do understand point 2 but I don't know what should I do with point 1 and 3. Please be little bit more descriptive for dummies... Thank you



    Hi,
    your quote points to an outdated posting from the Beta test timeframe of WHS.
    1. is refering to a website, which is used to post bug reports in a way, that the WHS developer team can evaluate them and get the informations they need. Better outlined in this thread and subsequent links.
    3. Is no longer valid, since it is refering to a beta version of Power Pack 1 (which is released in the meantime).

    No idea about error numbers like that. But maybe the dev team has. What is happening exactly?
    Best greetings from Germany
    Olaf
    Thursday, November 20, 2008 10:15 AM
    Moderator