From: Nathan M. <nat...@gm...> - 2015-06-21 21:31:39
|
After some testing it seems that if I create a batch script and call it through bash C:\cygwin64\bin\mintty.exe /bin/bash -l -c /usr/sbin/mfschunkserver then it seems to work fine without the 100% CPU utilization. So this is ultimately probably not a MooseFS issue. Sorry for the false alarm, and I hope this helps someone else who might have the same issue, (if anyone else is trying to run MFS processes on Windows that is). On 6/20/2015 10:51 PM, Nathan Morrison wrote: > Hi, > > First off I really like MooseFS. Mostly becuase it actually works on > Windows (once compiled with and running through Cygwin). I'm not sure > if it was coded that way purposely or not but I appreciate it (even if > Client portion must be run on Linux/Mac/BSD). > > Anyway, my problem is that once I have compiled it and run it on > Windows 7 Pro it takes 100% of a processor's cycles. Since it seems > to take advantage of only one core it takes only 25% total CPU on say > a quad core CPU (thankfully). But this is still burdensome to the > client and wastes electricity if nothing else. Setting the nice level > in the config helps but I'm looking for a better solution if possible. > > I of course don't experience this on my linux or RasPi2 clients > (however those are also not self compiled versions either, I'm > apt-getting them from repo). > > Any ideas How to fix this? > |