CPU Usage 100% all the time - is this normal?
Question
Answers
All replies
-
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
-
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.
-
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
-
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:
pen: 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.MP3When 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.
