Announcement

Collapse
No announcement yet.

S@H and G@H at the same time ?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • S@H and G@H at the same time ?

    As anyone ever tried this ?

  • #2
    I didn't try it, but from the Stanford FAQs...

    <font face="Verdana, Arial, Helvetica" size="2">Can I run Genome@home when SETI@home and/or Folding@home is running?

    Yes. Genome@home should run fine while SETI@home and/or Folding@home is running, assuming that you have enough RAM for both.
    </font>
    Furthermore, some people have had some better production while running two instances of g@h (some, like me, got worst too), so it should work. This puzzles me though, since one instance of a program takes up about 99% of the CPU's resources...

    But if I can remember correctly, someone tried this and saw that program priorities were not the same (both submissive), so what actually happened was that S@H stayed idle while G@H was computing, running only when g@H was uploading new data units.

    So, it probably will work, but it probably isn't worth the hassle.

    Someone back me up here!

    Fred

    Comment


    • #3
      Consider yourself backed up Fred...

      Fred is correct. It would not be worth the hassle - unless you are running under an SMP OS like Win2K and have 2 processors. Then you could dedicate 1 processor to each.

      Guyver
      Gaming Rig.

      - Gigabyte GA-7N400-Pro
      - AMD Athlon 3200+ XP
      - 1.5GB Dual Channel DDR 433Mhz SDRAM
      - 6.1 Digital Audio
      - Gigabit Lan (Linksys 1032)
      - 4 x 120GB SATA Drives, RAID 0+1 (Striped/Mirrored)
      - Sony DRU-500A DVD/+/-/R/RW
      - Creative 8x DVD-ROM
      - LS120 IDE Floppy
      - Zip 100 IDE
      - PNY Ultra 5900 (256MB)
      - NEC FE950
      - DTT2500 Cambridge Soundworks

      Comment


      • #4
        Well, I've always run seti@home alongside Genome@home...

        The way I runs it is genome as "belownormal" and seti at idle. This way seti only does significant work then genome tries to connect or it crashes, or I pause genome.

        If all is run as idle, most of the time they get equal cpu-time, but VLAR-wu in combination with affinity-lock don't work if seti & genome has the same priority.

        Comment

        Working...
        X