Announcement

Collapse
No announcement yet.

Work unit times...

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

  • Work unit times...

    Just wondering average times for different machines/OSes. Can you post experiences of processor/cache/chipset and OS please. I'd like to compile a list of as many machines as possible.

    Not sure about my own machines (damn last 10WUs stats still down - maybe the next downtime they can add that )
    P3-500, 512k, ZX, Win2k: 6 hours
    P2-350, 512k, BX, Win2k: 9 hours
    P120, ?k, ?, Win95: >24 (Laptop running 24/7: never checked)
    A couple of friends machines: Unknown!

    Thanks,

    Paul.

    ------------------
    Pace3000 Network: (early stages)
    Arena | Seti | P3K | TechSupport | Portal
    Matrox Users / SETI@MURC
    Join the team! | Crunch faster! | View the stats!
    Meet Jasmine.
    flickr.com/photos/pace3000

  • #2
    I can add a few to that list (and I assume we're talking current CLI version here):

    P3-500, 512k, ??, WinNT4: 6.8-7.4 hours
    P3-450@558, 512k, BX, Win98 2nd: 5.5-6.1 hours

    I'd like to point out though, that one of the most important things (even more important than processor speed), memory timing, is missing here... let me know if you want to include that.

    Comment


    • #3
      P3-750@825, 256k L2, BX@110, 256MB SDRAM 2-2-2, Win98 CLI: 6 hours or less

      Comment


      • #4
        Ok I have posted on this topic before but here goes ....

        PIII@667, 256kb, VIA Apollo 133A, 128Mb@133 3-3-3, Win98, SETI v2.04. Average time around 10 hours best time around 7 hours.

        I seem to get the best times if I leave SETI running and don't interrupt it or run any other programs at the same time.

        From what you all say I'm sure I should be getting better times. Still haven't tried the CLI version though.
        XP1800+ MSI 746Ultra 256Mb Corsair PC2700 MSI GF4800SE SBLive! WD 80GB 7200 DVD CDRW

        Comment


        • #5
          (just lost an attempt to post so here is a summary - it was a long post - DOH!)

          Kruse: yea, CLI

          Seaspray: Screensaver times inflate the CPU time by measuring running time - even if system is busy and giving it 0% attention. CLI measures actual CPU time so 10% of 10 hours counts as 1 hour in CLI yet 10 in GUI.

          I once found a WU which was at 56 hours in the GUI (my 3rd WU!) - I used the GUi but didn't like it - I only became really interested in Seti after I got the CLI - and Maggi gave me a batch script.

          Faster RAM is a major boost - try 2-2-2 at lower FSB.

          Paul.
          Meet Jasmine.
          flickr.com/photos/pace3000

          Comment


          • #6
            Pace, afaik win9x doesn't have an documented way to get cpu-time, so under win9x the cmd-line have the same time-bug as the gui-version.
            NT4 and later have a way for programs to get actual cpu-times.

            Comment


            • #7
              Yea - ok I'll include it then - can you's add FSB and RAM timing.

              P3-500, 512k, ZX@100, 128M/222, Win2k: 6hr
              P2-350, 512k, BX@100, 256M/222, Win2k: 9hr
              The other machines? Hell I don't even know the RAM off-hand!

              Paul.
              Meet Jasmine.
              flickr.com/photos/pace3000

              Comment


              • #8
                Pace&Rattledagger under win9x you can use WinAccelerator to do just that! http://www.tweakfiles.com//allinone/winaccelerator.html
                According to the latest official figures, 43% of all statistics are totally worthless...

                Comment


                • #9
                  Guru, does this utility pass the times back to seti@home so the averages doesn't get screwed up?

                  Comment


                  • #10
                    The gui-version is only using run-times.
                    As for win9x, I don't think there is a difference from before.

                    Comment


                    • #11
                      I used to use the 'Last 10 WU' page on Seti's site to judge times - so is the CLI under Win9x still giving out running time rather than CPU time?

                      And does the GUI measure run time or CPU time in NT?

                      Paul.
                      Meet Jasmine.
                      flickr.com/photos/pace3000

                      Comment


                      • #12
                        PII 233 @ 280 ,512K L2 ,112 MHz FSB ,BX chipset, CAS2 ,SDRAM precharge enabled ,average 10.5 hrs.Win 95c

                        As above but with PIII 700 @ 787MHz ,average 5.9 hrs

                        Cel 366 @ 550,100MHz FSB ,CAS2 RAM, 128K L2 cache,BX chipset ,average 7.9 hrs

                        ------------------
                        I guess I won't recruit for my team here Team Anandtech
                        Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, Asteroids@H, LHC@H, Skynet POGS.

                        Main rig - Q9550 @3.6 GHz, HD 5850 (Cat 13.1), 4GB DDR2, Win 7 64bit, BOINC 7.2.42
                        2nd rig - E5200 @3.73 GHz, GTX 260 c216, 4GB DDR2, Win XP, BOINC 7.2.42

                        Comment


                        • #13
                          Running Screen Saver 5 min delay, 0 min before blank.
                          See Sig: about 4.5 hr.
                          chuck


                          ------------------
                          ABit BF6, P3-650@923, 256mb@142cas3, 10gb IBM@7200, SB Live Value@3.0, Pioneer 104s DVD, Mitsumi CDRW@2x2x8, Acatel 1000 ADSL@1.5mb/sec, Linksys EtherFast NIC, LG 995e, USB mouse,Matrox G400 MAX!!!!

                          [This message has been edited by cjolley (edited 07 September 2000).]
                          Chuck
                          秋音的爸爸

                          Comment


                          • #14
                            Hey, I'm back so I'll update those stats I posted earlier... better late than never...

                            P3-500, 512k, Unknown chipset@100, 128M/333, WinNT4: 6.8-7.4 hours
                            P3-450@558, 512k, BX@124, 256M/222, Win98 2nd: 5.5-6.1 hours

                            Comment


                            • #15
                              P2-350/100/512k - ~9 hrs
                              p3-650/100/256k - ~6.5-7 hrs
                              p3xeon-800/133/256k - ~5-5.5 hrs

                              -=-=-
                              Andrew

                              [This message has been edited by agallag (edited 07 September 2000).]
                              Lady, people aren't chocolates. Do you know what they are mostly? Bastards. Bastard coated bastards with bastard filling. But I don't find them half as annoying as I find naive, bubble-headed optimists who walk around vomiting sunshine. -- Dr. Perry Cox

                              Comment

                              Working...
                              X