Announcement

Collapse
No announcement yet.

In the middle of the night/ I'm doing my first WU/ And it's only at 1 percent

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

  • In the middle of the night/ I'm doing my first WU/ And it's only at 1 percent

    2k,
    that depends on what applications you are running. Thought the norm, for swap-file size was 2.5xRAM, that would be 320MB in your case. Take a look on how much of your swap-file that's in use, that'll give you a clue.

    Jan


  • #2
    In the middle of the night/ I'm doing my first WU/ And it's only at 1 percent

    1 percent in 14 minutes
    100 percent in x

    let's see, 1400 minutes kind of grim, don't you think ? (23 hours, yuk)

    is this normal for a Pentium 3 (Katmai) with 128 megs of ram ?


    Comment


    • #3
      wich of the command line versions is the one for me ?
      http://setiathome.ssl.berkeley.edu/unix.html

      Comment


      • #4
        If it is 23hrs then no ,that's not normal.

        You should get about 8-9 hrs/WU.

        If you are using the screensaver version ,then make sure you have set 'blank screen' in the screen saveer settings to between 1-5 mins & check the box too
        That will roughly halve WU times.


        Damn! their I go again helping rival team members!

        ------------------
        I guess I won't recruit for my team here TA
        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


        • #5
          For Windows 95,98,NT, or 2000 use Winnt-commandline386 2.4

          ------------------
          I guess I won't recruit for my team here TA
          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


          • #6
            The exact file name listed is "i386-winnt-cmdline.exe". Give that a shot if you want to try the command line version. Also you might want to inquire about how to setup a local cache of WUs (work units). That's been covered in a few threads in the past, though I don't have their titles handy...

            Charles
            A few computers, some with Matrox stuff...I'll add details later.

            Comment


            • #7
              It's the same thing, whether I set none to screensaver or set the Seti one at 1 or 5 minutes (didn't try something between)
              Anyway, I have set the "Data analysis" to always on.

              The command line version is stuck at "Doing baseline smoothing", what should it show after that ?

              One hour and a lousy 4%. If this keeps on I'm finishing it in 25 hours

              [This message has been edited by 2K (edited 31 May 2000).]

              Comment


              • #8
                That is normal for the commandline ver.
                It is not stuck. It's just not wasting time on io.
                chuck
                Chuck
                秋音的爸爸

                Comment


                • #9
                  Does a permanent swap file affect SETI performance ? (256 in my case)

                  Comment


                  • #10
                    Up

                    Date problem with the forum again.

                    Comment


                    • #11
                      JMS

                      That old rule of 2.5 x RAM amount for swap file no longer applies.
                      Just stick it to 200Mb and be done with it

                      I was going to post a link to site with a article all about it but the sites add isn't valid anymore ,I'll see if I can find it under another name.
                      (in case your wondering it was http://epsilon.silicon.net.my/adrian/news.htm)

                      BTW permanent swap file will NOT adversly effect WU times.I have a fixed swap file and My Celeron 366 @ 578MHz on CLi v2.4 does a WU between 7hrs 15 mins to about 7hrs 45 mins if left alone.

                      2k

                      Did you check the blank screen box?
                      When left to 'always run' did you minimise the window?

                      If it's none of the above have you got some kind of Task manager to see how much cpu utiliastion SETI is getting?

                      If you want to see the output of the CLi v2.4 add -verbose to the commandline

                      ------------------
                      I guess I won't recruit for my team here TA
                      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


                      • #12
                        Norton System Doctor says it's using 99%-100%

                        Here's some data about the WU

                        Under Data Analysis:

                        Doppler drift rate: 3.6157 Hz/sec Resolution: 0.075 Hz
                        Best Gaussian: power 0.86, fit 5.037

                        under Data Info:

                        From: 19 hr 38' 45" RA, +18 deg 0' 36" Dec
                        Recorded on: Mon Mar 13 13:22:59 GMT
                        Source: Arecibo Radio Observatory
                        Base Frequency: 1.419189453 GHz

                        the graph:
                        Frequency (Hz) 9765.620
                        Time (sec) 107.4

                        Is there anything special about the WU ?
                        (13 mar, 13 hours, something to do with luck ?)

                        25% in 9 hours, I am going to finish it even at this rate, just to see if the next one goes this slow. If it does... well, I don't know.


                        [This message has been edited by 2K (edited 31 May 2000).]

                        Comment


                        • #13
                          Hmm, Norton System Doctor - have you tried disabling this?

                          Paul.

                          PS: This cache thing - at the mo' I run 3 or 4 copies of cmdline overnight on different priorities (Win2K) giving me slightly slower WU times than I might expect - can anybody tell me *exactly* how to do this run until finished then start another batch file under NT/2K and 98 as well - Maggi? Anybody? Thanks! (from me & seti@murc!)
                          Meet Jasmine.
                          flickr.com/photos/pace3000

                          Comment


                          • #14
                            I'm using GUI 1.06 running in the background at all times, with total CPU usage, and have 6 to 8 hours WU's on my P3-450 !!

                            Jord.
                            Jordâ„¢

                            Comment


                            • #15
                              Pace, the caching goes like this:

                              seti.bat
                              cd dir01
                              seti.exe -stop_after_process
                              cd ..\dir02
                              seti.exe -stop_after_process
                              cd ..\dir03
                              (continue to your last dir)
                              cd ..
                              seti.bat (repeats the bat-file)

                              Note: If you come to an already done work-unit, but not uploaded, it will try uploading the result. If impossible to upload, it will try again next hour.. and the next...


                              Make another file for uploading done units and getting new units:
                              upload.bat
                              cd dir01
                              seti.exe -stop_after_xfer
                              cd ..\dir02
                              (continue to your last dir)
                              cd .. (do not loop this)

                              You can run upload.bat then you want to. If no work-units is done or missing, nothing is done at all. You don't need to stop seti.bat

                              You should probably have a cache for 2-5 days, in case you comes across some 4-minutt-units, or the server is down.
                              No unit should be older than 7 days before returning.

                              Comment

                              Working...
                              X