Dual Processor Running Seti???
Home | Reviews and Features | Special Reports | Forums |

Results 1 to 6 of 6

Thread: Dual Processor Running Seti???

  1. #1
    Join Date
    Nov 1999
    Location
    Elmhurst, New York
    Posts
    626

    Dual Processor Running Seti???

    The FAQ on Seti@home's page wasn't too clear for supporting Dual processors. Maybe you guys can help. I just installed Seti on a Dual PIII 450@558 running WIn2K 392MB Ram. In Seti, do you have to change any settings so that it recognizes both processors and uses them. Or does it do it automatically like the RC5 client?

    ------------------
    Good Artist Copy, Great Artist Steal!
    Good Artist Copy, Great Artist Steal!
    http://www.pcguru2k.cjb.net
    [PGR2K]

  2. #2
    Join Date
    Jan 2000
    Location
    Norway
    Posts
    541
    you can run 2 wu`s in win2k and set them to use diferent cpu`s that is faster overal than runing just one.
    to set up tou just hit ctrl alt del and rightclick on the seti prosess and set priority and cpu.
    TNproud2b can probably tell you more.

    ------------------
    There are those who think, and those who dream, But I, for one, refuse to choose between the two!
    There are those who think, and those who dream, But I, for one, refuse to choose between the two!
    Xriz`s Place

  3. #3
    Join Date
    Aug 1999
    Location
    North Carolina
    Posts
    1,750
    Just run your SETI work units in individual folders. Use the command line version, of course. I do not assign individual processors for each work unit, Windows2000 manages that for me. I do have my system optimized for background services, but that's all I changed.
    I have 6 different SETI folders, all have a desktop link so i can start them with a single click. I generally run 2 at a time because that seems like the most efficient way. I can run a single work unit in about 8.5-9.5 hours @ 550MHz, but if I run 2 at a time It finishes both in about 13 hours. Running 3 or more slows me down to an average of about 10hrs/WU because it takes 30 hours to complete a set of 3.
    I don't know all the tricks, hell, I'm getting beat. Ask some of those guys that are ahead of me...
    P4 2.8@4.0 dual R134A phase change chillers with 600watt thermoelectric array. Capable of -70F
    Nixie tube numeric display control panel and pneumatic motherboard tray.

  4. #4
    Join Date
    Sep 1999
    Location
    Vienna, Austria
    Posts
    944
    Definitely one CPU per WU on Win2K.
    Its the (overall) fastest way to run it.

    Do not alocate the CPU yourself unless there are some other peculiarities of your system that require you to do this.

    You will probably get one WU/~7hrs running one SETI on one CPU, and around two WUs/~9hrs using two SETIs and two CPUs (one on each, managed by system).
    One SETI instance will finish before the other...like 90 mins before the other - dont be alarmed if its even more.

    Do NOT set the priority of SETI to high, even on dual CPUs. This is only funny when its someone elses machine ;-)


    ------------------
    // Black Holes are where God divided by zero //
    // Black Holes are where God divided by zero //

  5. #5
    Join Date
    Jan 2000
    Location
    Norway
    Posts
    541
    No, set the priority to realtime
    There are those who think, and those who dream, But I, for one, refuse to choose between the two!
    Xriz`s Place

  6. #6
    Join Date
    Nov 1999
    Location
    Elmhurst, New York
    Posts
    626
    Thanks a lot you guys! I should be catching up to all of you on the Seti ranks in now time :-) definitely gonna setup another machine this weekend when I'm free.

    ------------------
    Good Artist Copy, Great Artist Steal!
    Good Artist Copy, Great Artist Steal!
    http://www.pcguru2k.cjb.net
    [PGR2K]

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •