[uochris]

Is anyone using this yet? I'm just about to finish a work unit so I haven't installed it yet in case it resets my progress. Will this make stats meaningless if some people are using previous versions that are faster than this or will they stop accepting stats from old clients at some point? Just curious. Download version 4 here.

[sideus]

It picked up where the old version left off for me.

[chris v]

Is the new client multiprocessor aware? If not, can you set it up like the SETI CLI client, with two versions in diff. directories, one for each processor?

CV

[OneMacGuy]

Originally posted by chris v:
Is the new client multiprocessor aware? If not, can you set it up like the SETI CLI client, with two versions in diff. directories, one for each processor?

CV

I do not think that they changed the client to automatically use a second processor, but you can run two CLI clients simultaneously. Just use the -local switch when you execute the cleint in a terminal window and it will keep the work unit data in the directory that you execute it from, not the default location.

[mikkyo]

You guys should run
top -ud
in Terminal while running the new client and take a look. (q quits top)

On my single processor G3 with just one install, there are now 2 FahCore_78 processes running.
So with 2 processes running on a single processor, running on a dual processor machine you should get full cpu utilization with just 1 client.

Looks like it is smart enough to run at least 2 processes now, which probably explains any speed boost any one is seeing.

[OneMacGuy]

Originally posted by mikkyo:
You guys should run
top -ud
in Terminal while running the new client and take a look. (q quits top)

On my single processor G3 with just one install, there are now 2 FahCore_78 processes running.
So with 2 processes running on a single processor, running on a dual processor machine you should get full cpu utilization with just 1 client.

Looks like it is smart enough to run at least 2 processes now, which probably explains any speed boost any one is seeing.

I am running one instance of the new V4 core on a dual G4/533 and I only see one FahCore_78 process running under top. I do have an FAH4 process running also, but it is using 0% CPU.

[chris v]

FAHCore_78 is getting 100% CPU, but there is only one core running. I saved a copy of the client into another direcrory and ran ./fah4 -local, but the terminal spit out:

A potential conflict was detected:

Process 1867 is currently running and may also be a client with Mach. ID 1.
Program will now exit. Upon restart, this check will not be done --
you may wish to check that no client is currently running in
/Users/chrisvre/Library/Folding@home before restarting. (which is in fact where the current running core is located)

Is this a bad thing, or should I ignore the warning and restart the second client anyway?


CV

[reader50]

Do a fresh install for the 2nd folder. Duplicating the first folder gives the 2nd one the same Machine ID as the first process, and a copy of the same work unit to crunch.

[chris v]

Originally posted by reader50:
Do a fresh install for the 2nd folder. Duplicating the first folder gives the 2nd one the same Machine ID as the first process, and a copy of the same work unit to crunch.

It looks like you can change the machine id in the advanced settings. I'll try that.

CV

[reader50]

You can, but it would still leave you with the duplicated work unit. Depending on unit size and machine speed, you could lose up to a week of crunching before it fetched unique work.

[reader50]

For anyone interested, here is the Mac change log. Nothing is mentioned about automatically using dual CPUs.

------------------------------------
RECENT CHANGES (Client):

4.00:

• If client run with verbosity of at least 5, FahCore_78 will print out a
  message whenever a timered checkpoint occurs.*
• Benchmarking not done except at start of normal operation (for example,
  not if only configuring, listing queue, deleting unit, etc.).
• Warning if attempt to run client with Machine ID of already running client (catches
  most common cases, including if running same client twice)
• Web site printed updated.
• Upon finishing a unit, if fails to return the result but succeeds in
  getting new work, immediately tries sending all results again.
• Checks user name and team number for legality of use in statistics.
• Queue info properly outputted to FAHlog.txt.
• Proxy password written out in binary (upon reconfiguration)
• Assignment/work server request authentication
• Send all message altered ("sent x of y" if x not 0, or "no units...")
• CPU usage default of 100 printed out during Configuration.
• Tags in MyFolding page changed to better adhere to HTML standard
• Maximum machine IDs raised to 8.
• Upload and download bandwidths estimated to send to AS.
• If fails to post data, includes server and port in message. Also outputs
  HTTP status code (before this was only done if I.E. settings used).
• Bug fixed where performance fraction could exceed 1.

CLI specific-

• Configurable minimum checkpointing frequency (3-30 minutes).*
• -configonly flag added to configure then exit.
• -oneunit flag added to exit after completing one unit.
• Warnings printed if -forceasm/-forceSSE flags given.

GUI specific:

• Can open MyFolding page from menu.

* Items with an asterisk require FahCore_78.exe v. 1.53 to be functional -- certain
work servers are already forcing downloads of this core.

[mikkyo]

Well got me then.
Maybe I'm the only one lucky enough to have the double core client.
Wacky.
I wonder if it is RAM dependent or something?
Or a special version of the core?
What is funny is when I updated my dual it did it too.
Instead of two instances of the fah core I got 4.

[sideus]

On my Dual G4, had to install two instances to get two cores.

[Scotttheking]

Originally posted by mikkyo:
Well got me then.
Maybe I'm the only one lucky enough to have the double core client.
Wacky.
I wonder if it is RAM dependent or something?
Or a special version of the core?
What is funny is when I updated my dual it did it too.
Instead of two instances of the fah core I got 4.

I'll raise ya

Code:
scott@devbox:~$ ps aux | grep Fah
scott    22368  0.0  1.6 26776 8592 pts/1    SN   04:53   0:00 /usr/bin/wine.bin FahCore_78.exe -dir work/ -suffix 00 -forceasm -lifeline 55?
scott    22369  0.0  1.6 26776 8592 pts/1    SN   04:53   0:00 /usr/bin/wine.bin FahCore_78.exe -dir work/ -suffix 00 -forceasm -lifeline 55?
scott    22370  0.0  1.6 26776 8592 pts/1    SN   04:53   0:00 /usr/bin/wine.bin FahCore_78.exe -dir work/ -suffix 00 -forceasm -lifeline 55?
scott    22371 99.4  1.6 26776 8592 pts/1    RN   04:53 1010:31 /usr/bin/wine.bin FahCore_78.exe -dir work/ -suffix 00 -forceasm -lifeline 55?

One client, 4 cores. Note that only one is actually doing anything though.