Windows SMP Open Beta

SPIKE09SPIKE09 Scatland
edited August 2007 in Folding@Home
get your dual/quad cored windows boxes fired up folks.
http://forum.folding-community.org/viewtopic.php?t=18531&highlight= :D
«1345

Comments

  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    YES! Ah, some of us live for developments like this!

    EDIT: In case you are reading this thread and wonder what "SMP" is, it is Symmetric Multi Processing. What SMP accomplishes for Folding@Home synchronize both cores of a dual core CPU or two CPUs in a dual-CPU computer to work on the same work unit.
  • miragemirage
    edited March 2007
    Thank you for the heads-up. I am testing now on one of the two dual-core Windows machines. :D
  • ThermalfishThermalfish Melbourne, Australia
    edited March 2007
    Yup, chewing along here.
    SMP gromacs working well on this new Intel-based macbook.
  • Ultra-NexusUltra-Nexus Buenos Aires, ARG
    edited March 2007
    Now there are no more excuses! Lets get SM´s PPD boosted again! :D
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    I've got SMP for Windows installed on my System No. 3 now. We'll see how it goes.
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited March 2007
    added my 5000+

    will add a C2D E6700 on Monday.

    Thanks for the heads up, spike!
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    Lets get SM´s PPD boosted again!
    Let's hope so, but keep in mind the Windows SMP client is beta. It may just be Stanford's disclaimer, but they have warned us to expect bugs and incomplete work unit processing.

    Now, what Folding monitor will work correctly with SMP? I am currently running both FAHMon and EMIII.

    EMIII: the EMIII panel does not correctly identify the protein, and does not register points, elapsed frames, or time remaining. Maybe WeatherMan will update it soon. The FAHLog is displayed correctly, but then, it's a simple .txt file.

    FAHMon v2.1.5: displays the FAHLog.txt correctly

    I am addicted to accurate monitors. I'm like a floor worker at a stock exchange watching the stock issues monitor.
  • GargGarg Purveyor of Lincoln Nightmares Icrontian
    edited March 2007
    Hey Leo, do you have Hyper-Threading enabled? I think I read somewhere that the SMP client prefers 4 logical processors whenever its available.
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    No, my home computers all have D9xx series CPUs. They are dual core, 65nm, but do not have HT. HT went out the window with the advent of Conroe, except for Xeon Conroe-based dual core CPUs have HT, and I think also the EE edition(s).

    At this time, Stanford is recommending against enabling hyperthreading. Some users though, are reporting success with HT enabled.
    I think I read somewhere that the SMP client prefers 4 logical processors whenever its available.
    That may be. Task Manager, on the system in which I have SMP installed, shows four four FAH executables, for total CPU utilization of about 98-99%.
  • GargGarg Purveyor of Lincoln Nightmares Icrontian
    edited March 2007
    Leonardo wrote:
    No, my home computers all have D9xx series CPUs. They are dual core, 65nm, but do not have HT.
    Ah, I was wondering about that. I looked up the Pentium Ds on Wikipedia, but it didn't say if Preslers had HT or not.

    Found that passage I was looking for in the SMP faq:
    The SMP client was originally intended for multi-core CPUs, which generally do not support HT. For machines with 2 physical CPUs, we do recommend enabling HT for the SMP client as this presents the operating system with what looks like 4 logical processors (and our SMP client is intended for 4 processors). If you have 4 physical CPUs, we do not recommend using HT, as this presents the operating system with 8 logical processors, which will make the SMP client run inefficiently (especially since the logical processors coming from HT run much slower than the normal ones).
    Off the top of my head, I think the only dual core CPUs out there with HT might be Extreme Editions. Maybe some Xeons, too? I sort of tuned out on CPU tech after Athlon XPs. :)
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    I sort of tuned out of CPUs until after dual core caught on with the D8xx series. Then with the die shrink to 65nm (Presler core/D9xx) I really became a fan.

    The dual core Xeons are, for a fact, HT. A dual core Xeon will run four threads with relative ease, but of course, not as well as a four-core CPU.

    Thanks for posting the quote. Informative.
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    Monitor Windows SMP Folding Production:

    Go here for instructions

    Go here for the necessary FAHMon version 2.1.5b.5 (customized)
  • DonutDonut Maine New
    edited March 2007
    When somebody knows, could they post the points difference between the 64-bit Linux client vs. the Windows client? I've got 2 rigs here that could be switched back to Windows if I don't loose to much production. Me + Linux=DUH!

    When this shut-down season winds down I'll install on my dual Xeon rig.
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited March 2007
    I can't use it at all on my X2/5000+ system. It errors out constantly and re-downloads units, as well as hard-locking my system once :(

    No SMP for me, yet...
  • GargGarg Purveyor of Lincoln Nightmares Icrontian
    edited March 2007
    So far so good for me, but I've only been running it for a couple of hours. About 32 minutes/frame on my 2.4ghz Opty.

    Does anyone know if the Windows client has a problem with resuming work after the console is closed? Apparently that used to be a problem with the Linux client.
  • miragemirage
    edited March 2007
    Donut wrote:
    When somebody knows, could they post the points difference between the 64-bit Linux client vs. the Windows client? I've got 2 rigs here that could be switched back to Windows if I don't loose to much production. Me + Linux=DUH!

    When this shut-down season winds down I'll install on my dual Xeon rig.

    Comparing running P2605 (1760 points) on Linux and P2610 (1523 points) on Windows, they both take 25m per frame on 2.6GHz Opty165 (Linux) and 2.8 GHz Opty165(Windows). Based on the points and slightly faster processor of Windows, I would expect P2610 to be running faster. The point assignments might be off, but I have the impression that WinSMP is not as efficient as LinuxSMP. Just an initial impression, but I recommend hanging on Linux, at least for now.

    Okay okay, let me say this way: please don't leave Linux pleaaaaase. :bigggrin:
  • miragemirage
    edited March 2007
    Gargoyle wrote:
    So far so good for me, but I've only been running it for a couple of hours. About 32 minutes/frame on my 2.4ghz Opty.

    Does anyone know if the Windows client has a problem with resuming work after the console is closed? Apparently that used to be a problem with the Linux client.

    I am shutting down the Windows computers every night. They restarted the SMP jobs in the morning normally. And yes, I will catch the tight deadlines as well.
  • Sledgehammer70Sledgehammer70 California Icrontian
    edited March 2007
    will slam it on my work PC's in the morning :) well atleast one for testing :)
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    Ultra Nexus wrote:
    Now there are no more excuses! Lets get SM´s PPD boosted again! :D
    Boosted indeed.:D:D I've started a production thread for Windows SMP. Go on over and post your results.
  • Sledgehammer70Sledgehammer70 California Icrontian
    edited March 2007
    Something isn't right :(
    OpenSCManager failed:
    Access is denied. (error 5)
    Unable to remove the previous installation, install failed.
    account (domain\user) [Sledgelappy\Sledgehammer70]:
    password:
    confirm password:
    Password encrypted into the Registry.
    Unable to connect to 'Sledgelappy:8676',
    sock error: generic socket failure, error stack:
    MPIDU_Sock_post_connect(1228): unable to connect to Sledgelappy on port 8676, ex
    hausted all endpoints (errno -1)
    MPIDU_Sock_post_connect(1275): unable to connect to Sledgelappy on port 8676, No
    connection could be made because the target machine actively refused it. (errno
    10061)
    Press any key to continue . . .
  • miragemirage
    edited March 2007
    Sledgehammer70 wrote:
    Something isn't right :(

    I think you need allow mpiexec in your internal software firewall settings, or open up that specific port for mpiexec. :)
  • Sledgehammer70Sledgehammer70 California Icrontian
    edited March 2007
    Firewall is turned off, and all ports are open... well they should be for the most part.
  • miragemirage
    edited March 2007
    Sledgehammer70 wrote:
    Firewall is turned off, and all ports are open... well they should be for the most part.

    :scratch: But the error message is complaining about accessing the ports, something is stopping it. If not firewall, can it be a virus scanner? some of them control the ports as well.
  • Sledgehammer70Sledgehammer70 California Icrontian
    edited March 2007
    I think this is a bad error in the first place
    OpenSCManager failed:
    Access is denied. (error 5)
    Unable to remove the previous installation, install failed.
    account (domain\user) [Sledgelappy\Sledgehammer70]:

    I know it is a MPI error as in the readme it says if you see a -1 in the report it means the mpi isn't configured right. here is my F@H log
    Note: Please read the license agreement (fah.exe -license). Further
    use of this software requires that you have read and accepted this agreement.

    2 cores detected
    No directory settings found in registry. Using current directory...


    --- Opening Log file [March 19 19:48:40]


    # SMP Client ##################################################################
    ###############################################################################

    Folding@Home Client Version 5.91beta

    http://folding.stanford.edu

    ###############################################################################
    ###############################################################################

    Launch directory: D:\Program Files\Folding@Home Windows SMP Client V1.01
    Executable: D:\Program Files\Folding@Home Windows SMP Client V1.01\fah.exe


    [19:48:40] Configuring Folding@Home...

    User name [Anonymous]? sledgehammer70
    Team Number [0]? 93
    Opening Service Manager failed (5)
    Windows denied access for this operation.
    You must be logged on with Administrator privileges.
    Launch automatically at machine startup, installing this as a
    service (yes/no) [no]? no
    Opening Service Manager failed (5)
    Windows denied access for this operation.
    You must be logged on with Administrator privileges.
    Ask before fetching/sending work (no/yes) [no]? no
    Use Internet Explorer Settings (no/yes) [no]?
    Use proxy (yes/no) [no]?
    Allow receipt of work assignments greater than 5MB in size (no/yes) [no]?yes
    Change advanced options (yes/no) [no]?

    [19:49:02] - Ask before connecting: No
    [19:49:02] - User name: sledgehammer70 (Team 93)
    [19:49:02] - User ID: 32C0DEB9361E7ED5
    [19:49:02] - Machine ID: 1
    [19:49:02]
    [19:49:02] Work directory not found. Creating...
    [19:49:02] Could not open work queue, generating new queue...
    [19:49:02] - Preparing to get new work unit...
    [19:49:02] + Attempting to get work packet
    [19:49:02] - Connecting to assignment server
    [19:49:04] - Successful: assigned to (171.64.65.64).
    [19:49:04] + News From Folding@Home: Welcome to Folding@Home
    [19:49:04] Loaded queue successfully.
    [19:51:11] + Closed connections
    [19:51:11]
    [19:51:11] + Processing work unit
    [19:51:11] Core required: FahCore_a1.exe
    [19:51:11] Core not found.
    [19:51:11] - Core is not present or corrupted.
    [19:51:11] - Attempting to download new core...
    [19:51:11] + Downloading new core: FahCore_a1.exe
    [19:51:18] + 10240 bytes downloaded
    [19:51:18] + 20480 bytes downloaded
    [19:51:19] + 30720 bytes downloaded
    [19:51:19] + 40960 bytes downloaded
    [19:51:19] + 51200 bytes downloaded
    [19:51:19] + 61440 bytes downloaded
    [19:51:20] + 71680 bytes downloaded
    [19:51:20] + 81920 bytes downloaded
    [19:51:20] + 92160 bytes downloaded
    [19:51:21] + 102400 bytes downloaded
    [19:51:21] + 112640 bytes downloaded
    [19:51:22] + 122880 bytes downloaded
    [19:51:22] + 133120 bytes downloaded
    [19:51:22] + 143360 bytes downloaded
    [19:51:22] + 153600 bytes downloaded
    [19:51:23] + 163840 bytes downloaded
    [19:51:23] + 174080 bytes downloaded
    [19:51:23] + 184320 bytes downloaded
    [19:51:23] + 194560 bytes downloaded
    [19:51:23] + 204800 bytes downloaded
    [19:51:24] + 215040 bytes downloaded
    [19:51:24] + 225280 bytes downloaded
    [19:51:25] + 235520 bytes downloaded
    [19:51:25] + 245760 bytes downloaded
    [19:51:25] + 256000 bytes downloaded
    [19:51:26] + 266240 bytes downloaded
    [19:51:26] + 276480 bytes downloaded
    [19:51:26] + 286720 bytes downloaded
    [19:51:26] + 296960 bytes downloaded
    [19:51:27] + 307200 bytes downloaded
    [19:51:27] + 317440 bytes downloaded
    [19:51:27] + 327680 bytes downloaded
    [19:51:27] + 337920 bytes downloaded
    [19:51:28] + 348160 bytes downloaded
    [19:51:28] + 358400 bytes downloaded
    [19:51:28] + 368640 bytes downloaded
    [19:51:28] + 378880 bytes downloaded
    [19:51:29] + 389120 bytes downloaded
    [19:51:29] + 399360 bytes downloaded
    [19:51:29] + 409600 bytes downloaded
    [19:51:29] + 419840 bytes downloaded
    [19:51:29] + 430080 bytes downloaded
    [19:51:30] + 440320 bytes downloaded
    [19:51:30] + 450560 bytes downloaded
    [19:51:30] + 460800 bytes downloaded
    [19:51:30] + 471040 bytes downloaded
    [19:51:31] + 481280 bytes downloaded
    [19:51:31] + 491520 bytes downloaded
    [19:51:31] + 501760 bytes downloaded
    [19:51:32] + 512000 bytes downloaded
    [19:51:32] + 522240 bytes downloaded
    [19:51:33] + 532480 bytes downloaded
    [19:51:33] + 542720 bytes downloaded
    [19:51:33] + 552960 bytes downloaded
    [19:51:34] + 563200 bytes downloaded
    [19:51:34] + 573440 bytes downloaded
    [19:51:34] + 583680 bytes downloaded
    [19:51:34] + 593920 bytes downloaded
    [19:51:35] + 604160 bytes downloaded
    [19:51:35] + 614400 bytes downloaded
    [19:51:35] + 624640 bytes downloaded
    [19:51:36] + 634880 bytes downloaded
    [19:51:36] + 645120 bytes downloaded
    [19:51:36] + 655360 bytes downloaded
    [19:51:37] + 665600 bytes downloaded
    [19:51:37] + 675840 bytes downloaded
    [19:51:37] + 686080 bytes downloaded
    [19:51:38] + 696320 bytes downloaded
    [19:51:38] + 706560 bytes downloaded
    [19:51:38] + 716800 bytes downloaded
    [19:51:39] + 727040 bytes downloaded
    [19:51:39] + 737280 bytes downloaded
    [19:51:40] + 747520 bytes downloaded
    [19:51:40] + 757760 bytes downloaded
    [19:51:40] + 768000 bytes downloaded
    [19:51:40] + 778240 bytes downloaded
    [19:51:41] + 788480 bytes downloaded
    [19:51:41] + 789667 bytes downloaded
    [19:51:41] Verifying core Core_a1.fah...
    [19:51:41] Signature is VALID
    [19:51:41]
    [19:51:41] Trying to unzip core FahCore_a1.exe
    [19:51:41] Decompressed FahCore_a1.exe (2035712 bytes) successfully
    [19:51:41] + Core successfully engaged
    [19:51:46]
    [19:51:46] + Processing work unit
    [19:51:46] Core required: FahCore_a1.exe
    [19:51:46] Core found.
    [19:51:46] Working on Unit 01 [March 19 19:51:46]
    [19:51:46] + Working ...
    [19:51:54] CoreStatus = FFFFFFFF (-1)
    [19:51:54] Client-core communications error: ERROR 0xffffffff
    [19:51:54] Deleting current work unit & continuing...
    [19:52:02] - Preparing to get new work unit...
    [19:52:02] + Attempting to get work packet
    [19:52:02] - Connecting to assignment server
    [19:52:03] - Successful: assigned to (171.64.65.64).
    [19:52:03] + News From Folding@Home: Welcome to Folding@Home
    [19:52:04] Loaded queue successfully.
  • miragemirage
    edited March 2007
    Yeah, it looks like a serious error. First, you will install the WinSMP package you have downloaded. Then, you need to execute an installation script (BAT file) in the installation directory. During execution of this script I was asked by Windows' default firewall to allow mpiexec. Did you go through similar steps? If you can not uninstall, maybe you can try re-installing over the current one
  • Sledgehammer70Sledgehammer70 California Icrontian
    edited March 2007
    I wonder if it is because of Vista?

    Yes it asked to allow with firewalls and I said yes, and see them in the list of enabled actions under the firewall settings...
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited March 2007
    Sledge, I don't know know much about Vista's composition, so I may be off on this. With Windows XP, .Net framework (sp?) 2.0 must be installed for the MPI to function/access properly. Does Vista have .net 2.0 or the equivalent?
  • miragemirage
    edited March 2007
    Sledgehammer70 wrote:
    I wonder if it is because of Vista?
    Most likely. It is probably trying to protect you from mpiexec by assuming it to be spyware, etc. Do you have a security-center-like control panel in Vista? Maybe you can disable security components one at a time to find which one is causing this.
  • Sledgehammer70Sledgehammer70 California Icrontian
    edited March 2007
    Vista has 2.0 built in standard... as for security senter I have disabled everything and turned things back on one at a time and get nothing there.
  • miragemirage
    edited March 2007
    If you look at the following link, http://folding.stanford.edu/FAQ-SMP.html

    I am quoting a section from that page below

    **NOTE** The username and password you provide for mpiexec should be your Windows login that you will run the client under. This is used for authentication on your local machine. It is cached in encrypted form in your Registry and is not transmitted to FAH servers.

    Then, it might also be related to user access rights and/or incorrect password.
Sign In or Register to comment.