FAH SMP cannot get past this MPIEXEC error?

FatRakoon

FatRakoon

FatRakoon

Soldato
Joined
18 Oct 2002
Posts
10,448
Location
Behind you... Naked!
I have been running 4 clients of FAH for a while now, and a couple of times I have tried to go with one, but with the SMP switch enabled.

However, whenever I try to do it, I get this mpiexec not recognised as an internal or external command error and I cannot get past it.

I have looked at the info but I have not found a cure for that that actually works?

I am clearly a moron but I cannot see why? Can anyone help me out in "Peter and Jane" level nursery english please?

Thanks.
 
I was going to moan about how 6.34 is only available for Linux, and then I go to prove this to myself and I find not only 6.34 but 6.41 too - in the High performance clients list.

I will grab 6.34 however and give that a shot, so cheers
 
The error is normal, but you might have to wait awhile for it to move forwards to the first % as the SMP WU's are pretty hefty.

Post some of the log file next time its called FAHlog.txt
 
Ok, what I have done, is installed the 6.34 Client as BaBa suggests.

I am normally running 4 clients on 4 cores. I have named them FAH-A.EXE, FAH-B, C and D of course with each in its own DIR as I am supposed to.

They are running as a service, however, just finish their current jobs off, I ran them in a CLI using the -oneunit switch.

I then restarted with the SMP client, and I ran the -configonly -smp switches but its still only runnign on the one core... Well, its running it on all 4 cores, but its only taking up 25% of the total CPU but the normal one core version does this anyway.

I have included a link to the log file

http://www.fatrakoon.co.uk/fahlog.txt

And just in case its worth looking at, the client config file

http://www.fatrakoon.co.uk/client.cfg

To be honest, I am ok with running 4 clients because I can and sometimes do, simply turn one off now and then, plus I set the affinity for each to one core because whether I have the lock on or not makes no difference, but I would much rather one program that uses all 4 cores.

So, this 6.34 is doing the exact same as the other one I was using whatever version that was? 6.23 I think?
 
You may have run -configonly with the -smp switch but I'd bet you aren't running the client now with the -smp switch.

Also, get yourself a passcode as it will greatly increase the value of your smp WUs once you've completed ten of them.
 
From the log file I'd say you were right Snapshot.

FatRakoon: Run -configonly again, set it to get big workunits, but when it asks you, go into the advanced settings and set:
-smp -advmethods -verbosity 9
in the "additional client parameters"

Easiest way.

Oh yeah and make sure you have a Passkey
 
Ok cool.
Passkey now obtained. Bit surprised at the size of it... I have never seen a trillion bit hex code before LOL I printed it out for safe keeping and I run out of toner!

Ok, the switches are set, and reading the CFG file they are now showing up in there, so I will restart and see how it goes?
 
I have just reset, its still on one core, or 25% however its in the middle of a unit, so hopefully when it loads up the next work unit, it will start to work as I hope it will.

Only give it that time now then yes?

Thanks again guys, will update as soon as ...
 
Brilliant.

Cheers guys.

Just checked up on her, and FAH-C and FAH-D are both finished, A and B are almost done, so I will let them finish, but FAH-SMP has started a new one and thats eating up 46%

I closed off A and B to have a look and SMP then shot up to 96%

I have re-run A and B to let them finish off as I said, and then I set the affinity to 1,1, and 2 for them all 25%, 25% and 50% is now being eaten up just for cosmetic reasons more than anything.

Anyway, its done, and many thanks for that.

I was clearly missing the -smp switch again wasnt I!
 
You must log in or register to reply here.
Back
Top Bottom