Setting different CPU workloads

[DorianBrytestar]

Is it possible on a multi cpu or hyperthreaded or dual core system to set one cpu to only use 50% to fold and the others to run at a different rate? (75%)

My goal is that we seem to have a ton of servers that are hyperthreaded or dual core or even quad core, but no rteal applications that are utilizing those resourses much. I would like to tap into the sleeping cores and leave the main "first" core more open for any sort of workload. I understand the affinity should allow anything else to take over, but I would rather not peg all the cpus to 100 all the time.

[Jon]

Doesn't the client allow you to set the CPU usage when setting up under the advanced options?

CPU usage requested (5-100)[100]

Not sure if that offers the effect you want, but I would imagine it does.

[DorianBrytestar]

I saw that line, and modified it, but I am not seeing it really change the cpu usage. I put it on a quad box and set varying ranges of 100, 70, 50, 30 and the cpus are all still pegged at 100 or very near to it.

[dz_jad]

hmm, I guess that setting must be disabled for the SMP beta....assuming you are using the SMP beta..?
or are you just using the uniprocessor client?
and how are you 'changing that line'?

[ChasR]

Without knowing which client you installed there's not much we can do for you. I will say that Windows load balancing is very good and settting affinity is almost always unnecessary. In general, FAH gets out of the way fast enough that there isn't any need to run @ less than 100% except where overheating is an issue, as on laptops.

[DorianBrytestar]

I used the wedo's installs, I used the quad cpu version and also the dually/ht version.

These are on windows server 2003 for the most part, and to modify them, I just opened up the client.cfg file and changed the line in where it says cpuusage=100 and changed that value to 70,50,40, etc. I did this at the install when I changed my name as well.

[pscout]

I assume you stopped the client while you made the changes and then restarted it?

The client.cfg only gets read when the client starts up.

[DorianBrytestar]

Yeah, I made the changes before I even installed.

[pscout]

well, it was just a guess ... i have never played with the % or priority settings, at least not that i remember.

I just keep the pedal to the metal :D

[DorianBrytestar]

Hehe, well, I guess they'll just have to run wide open for awhile and we'll see if it causes any sort of problem. Those machines are not used for anything at all even slightly cpu intensive, so I can't see it being a problem. I just wanted to play it extra safe.


btw + 10 cpus.
:burn:



(PS. Interesting, judging by the progress of the units, the cpu setting is definately making a difference in how fast the work units are being completed. And the cpu does not stay at 100% on those set with lower cpu settings. It does jump up to 100 and then back down. So while ity is not pegging out at a smooth line at the desired setting like I thought it would, it's still close to what I was aiming for.)

[dz_jad]

Sweet! We welcome your new borg :D

[ChasR]

On the Quad with Win Serv 2003, in Task Manager you should have 4 FahCore_xx processes running. If cpuusage is set to 100% for all of them, each will show 25% cpu and CPU Usage (at the bottom of the window) should be pegged at 100% with no fluctuation. If not, CPU should show 25 x whatever % you set for the instance and CPU Usage should ramain well below 100% all of the time, unless something other than FAH is using the cycles you blocked from FAH use.

If you don't want to run 100% I suggest you set each instance to 75%, the equivalent of one free core and let windows do its job and balance the load rather than setting affinity. Since these WUs are serial in nature, running one on a processor @ 25% cpu usage will drastically slow the WU and delay the project.

[DorianBrytestar]

Ok, you've convinced me.

+10 cpus 100%!!!!!