Announcement

Collapse
No announcement yet.

How to make Genome@home go faster!

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

  • #16
    Cool...Thanx guys
    They work great together.

    Now has any one got a way to make the box title stay as GHClient in Win98? Win2K works fine with a link but on a new WU the title changes in Win98. This prevents GV from keeping the Client hidden.

    Mark F.

    ------------------
    OH NO, my retractable cup holder swallowed a DVD...
    and burped out a movie
    Mark F. (A+, Network+, & CCNA)
    --------------------------------------------------
    OH NO, my retractable cup holder swallowed a DVD...
    and burped out a movie

    Comment


    • #17
      Hold on...are you guys running two instances of Genome at once...? Or, is it something else?

      Comment


      • #18
        I have only one instance of Genome running now. But you can run two or more under your own name, if the server is playing it right. You just need the same name and email address to give to the G@H server, and you'll get several Genome ID's, one for every genome you start.

        As I found out though, you can only run one instance of Genome Voyeur at one time on one computer. But you can run a lot of G@H clients in different folders all running the same Unit. Or all running their own Unit, which needs all of their own ID's for Genome@Home. One and the same ID for multiple folders doesn't work !!

        Jord.

        [This message has been edited by Jorden (edited 16 March 2001).]
        Jordâ„¢

        Comment


        • #19
          Funny, I'm running multiple instances of Genome Voyeur here I'm sitting now. Maybe it's because I haven't upgraded from 0.20...
          For hiding, I'm using FireDaemon.

          Then installing multiple instances, the easiest is to install one copy, don't start the client, copy all files to other directories, run one instance and get correct name/team. Copy ghclient.cfg to all the clients.
          Then you execute them, you already has the correct info, and you don't get one client with typing-problems.
          As already said its important that you don't copy id.dat, but get this for all clients from the servers... if you can connect.


          As for the batch-file, NT don't use any slider for non-dos-programs, so of course the batch-file don't remember the priority.
          Ghclient.exe automatically sets the priority to idle then started. Filter.exe gets the same priority as ghclient.exe
          On the other hand, it does get the affinity from the batch-file, or cmd-line you're executing from.

          Comment


          • #20
            But why run multiple instances if you don't have dual CPUs? Or are are you guys implying I could run hundreds of Genome clients without slowdown?

            Comment


            • #21
              Hundreds LS? I don't know, never tried that

              My 2 running at the same moment were a fluke of the moment. I since then made 2 folders running their own G@H clients. I'm now down to 40 minute sequences, and no uploads due to the apparent G@H server down-being.

              So, one of my G@H's is crunching a 58aa, while the other is doing a 60aa.

              I must say the 40 minute sequences only work when I don't do too much inbetween, like type here at MURC

              Jord.
              Jordâ„¢

              Comment


              • #22
                So, you are running two instances right now, and you are getting more processing done? I'll have to try this myself

                Comment


                • #23
                  I'm running 2 units at once now (around 60aa) and it takes about 30 minutes per sequence on my Duron 900, I'm currently trying to get a third unit (damn that server) to see how much it affects sequence times.
                  "That's right fool! Now I'm a flying talking donkey!"

                  P4 2.66, 512 mb PC2700, ATI Radeon 9000, Seagate Barracude IV 80 gb, Acer Al 732 17" TFT

                  Comment


                  • #24
                    Not much faster running 3 units at the same time, around 2½ sequences per half hour, still an improvement, but one of the units slows to a crawl, running at less than half the speed of the others.
                    "That's right fool! Now I'm a flying talking donkey!"

                    P4 2.66, 512 mb PC2700, ATI Radeon 9000, Seagate Barracude IV 80 gb, Acer Al 732 17" TFT

                    Comment


                    • #25
                      Except the time then the client tries to connect, there shouldn't be any reason to run more instances than number of cpu's. Like Seti@home, Genome@home uses 100% cpu.

                      With a virtual memory usage on nearly 50MB your pagefile would soon fill up if you tries running many instances. Since the max pagefile-size per parition is 4GB, you must use two pagefiles to run over 80 instances.

                      Comment


                      • #26
                        From what I can see, I am running two instances right now, and there appears to be little or no slowdown.

                        Comment


                        • #27
                          Damn, both my G@H's are now trying to send the data to the G@H server. They've been trying to do so for the past 4 hours, and restarting one didn't matter. They won't recrunch, nor will they take new Units.

                          I am at a standstill.

                          How do I tell G@H to rerun my Units? I don't know anymore. Filter doesn't work either.

                          Jord.
                          Jordâ„¢

                          Comment


                          • #28
                            It's supposed to only try for 20 minutes, then it restarts the unit. Some others have reported this problem. I think .94 solves it, though I'm not sure. <A HREF="http://groups.yahoo.com/group/genomeathome/message/807">Here</A>.

                            Comment

                            Working...
                            X