Bubba wrote:Just joined... but don't get too excited just yet!
Current = 22% in... wait for it... 15 hours.
Surely a p3-750 shouldn't be this slow??!! Anything I can do to speed it up?
Cheers
Bubba
Theoretically you should be getting an average return time of 8hrs with a Coppermine P3 processor.
moobaa wrote:
Sir_LANs-a-lot wrote:Or run the NT command-line version (maybe with SETI Spy so you can queue up work units if their server is down).
Definitely run the command line version, it's noticably quicker.
Dunno whether you have to bother queuing work units at that rate, though
SETI Spy doesn't queue work units, you need to link it with SETI Driver (and maybe SETI Queue as well if you are paranoid about Berkeley's S@H server).
Hrm, I have a machine on setiQueue thats died mid-workunit.. can anyone tell me how to remove it from setiQueues display? The red widget is annoying me
randomdude wrote:Hrm, I have a machine on setiQueue thats died mid-workunit.. can anyone tell me how to remove it from setiQueues display? The red widget is annoying me
If you mean a WU that is half processed then point your browser at 127.0.0.1:5517 or whatever you set up the access to be. Then click on Login under the Admin bit (bottom left). Next select Tools under the Admin bit and then you can see a list of maintenance tools. You need 'Delete/Recycle an overdue workunit'.
If it is a WU that didn't return properly then ignore it. It will go away.
Now that I have my old m/c still churning out 1 unit per day and my new one turning SIX around, I shall be cracking the 1,000 mark some time tomorrow or early Friday. I am expecting a telegram from a small green creature, at the very least
Watch out, Muttley ... I'm coming up fast behind you
So yesterday I finally decided to try the SETI commandline version.
Using the GUI I've been getting WU times of 16-odd hours, which seemed a bit steep as I'm on a relatively new 2Ghz P4 Dell box, and my old 500Mhz IBM used to churn them out in around 9.5 hours. I know the WU logic changed a release or two back while I was off SETI for a while, so I assume this was the cause of the throughout drop - the box is tuned in all other respects, although of course being an office box its graphics hardware is nothing spectacular - so maybe that's not helping.
Downloaded the CLI version and ran it. Works fine, if a bit clunky - don't like the DOS box getting in the way. Read some docs about turning it into a service using the NT Reskit utilities INSTSRV and SRVANY. Do it. Works. Nice.
Now, how to monitor it? Scan the list of add-ons on the SETI site. Downloaded and installed SETIHide. Disabled service-mode, as this utility handles silent running of the CLI. Run it. Works. Nice. Go home.
Today, open the SETIHide client. 4.5 WUs processed overnight, average time per WU is 3h26m. Very Nice. Impressed.
Side note: set this same config up on the big box at home (AMD 2500+ oc'd to 1.99Ghz). Average WU time: 1h17m. Even Nicer.
So if you're looking for raw WU throughput, the CLI version is definitely the way to go.
Just discovered that I spoiled seven days on one single unit simply because I had a screen saver running all the time, that ate away all performance...
That did cost me the 8th place... but I'll get it back...
Here's the proof - 216,711th Wow! Don't take too much notice of the "25 Hours per Unit" - the new m/c is currently clocking under 4. Now, if the CLI version can be run on Win XP ... Anybody know??
Watch out, Muttley ... I'm coming up fast behind you 
Here's the proof - 216,711th 
Wow! Don't take too much notice of the "25 Hours per Unit" - the new m/c is currently clocking under 4. Now, if the CLI version can be run on Win XP ... Anybody know??
-
-lations, Ian 
Just discovered that I spoiled seven days on one single unit simply because I had a screen saver running all the time, that ate away all performance...