On Wed, 10 Sep 2003 22:43:45 +0000 (UTC), "Nick M V Salmon"
<spam_dump@btinternet.com> wrote:

"Roger Halstead" <newsgroups@rogerhalstead.com> wrote

"Nick M V Salmon" <spam_dump@btinternet.com> wrote:

There's no reason for _any_ work unit to take that much longer than

normal

without some problem somewhere - worst 'normal' case is a VLAR work unit
with a sub 0.1 angle range under a Windows '98 based O/S & they are

'only'

circa 50% slower than the average 0.417AR work unit.  Windows NT based

<snip>

I had 4 or 5 of these last this past Spring.   The only thing that was
heavily using resources was the seti client.  These were running on a
.19XP + Athlon.  I let one run. It had been projecting 53 hours, but
that kept getting bumped up.  Up around 58 hours it was saying 68...So
I flushed it and got a new WU.  Over the next few weeks I had several
more.  When a WU appeared to be taking longer than about 3X normal,
I'd flush it.  All of those WUs were indicating a projected finish
time of some where in the 50 hours range.

I've never had one since.

I've never seen a single one..!  Weird, were all these on the same 1900+
machine..?   I'd suspect some form of hardware fault or a corrupt SETI.exe &
go hunting myself...

You've jogged my memory a bit more.
After the second *long* WU, I replaced the client exe.  It ran about
three days and I had another long WU.  This would not be the same
client as I use a script file to run successive clients in different
directories.  Again, I just deleted the WU and downloaded another.
Again I ran into another long WU so I replaced the client exe.  I
don't recall replacing all of those exe files that had the long WUs,
but I may have.

I remember now that I did have one other machine that had one
extremely long WU in the same period.  I do not remember if I also
replace the client exe on that one or not.

The odds are fairly high on the one machine that something had trashed
a spot on the HD.  Those client exe files could have all been located
in the same area even though they are not sequential in the directory.

As the second machine had a problem during the same period it *might*
have been network noise, something trashing the HD, or corrupted WUs
on download. it could also have been coincidence.


Roger Halstead (K8RI EN73 & ARRL Life Member)
www.rogerhalstead.com
N833R World's oldest Debonair? (S# CD-2)

BTW: I have never had even a ONE work unit take that much longer than

normal

here - ie. 743% slower..!   I currently have 23,600 results returned and
that figure is increasing at roughly 74 results/day from 7 machines, all

I'm running 4. 2 1900s, a 2000 and a 2800. All Athlon XP +.  It's been
so long since I checked I'm not sure just how many WUs get returned
per week... High 200s "I think".  Some where between 1/3 and 1/2 of
what you are getting.

I've done 739 in the last ten days (Sept 1st 00.00 to Sept 11th 00.00)
according to SetiTeam - that's 73.9/day or 517/week.  I setup SetiTeam to
record on the 1st of each month so I can keep an eye on how I'm doing...

AMD.   Longest (wallclock) time WUs I get at the moment are whilst I'm

using

the 'TV on Demand' facility (Like a TiVo.) of my ATI All In Wonder Radeon
8500DV. (+30% or so above normal for that AR.)  That one's a real

resource

hog & would probably take all 100% of a 1.4GHz Athlon...

All mine run at 100% most of the time.  This one (the 2800) also gets
all my internet work, programming, and even FS9.  I use the CLI with
default settings.  The other programs including FS9 don't appear to
even realize the Seti client is even there.

Heh, I up the priority to 'normal' on all my WinME machines to cut the 0.2%
'wasted' by the idle loop and even then SETI only causes a barely noticeable
slowdown opening up software Etc.   I don't change the priority on any of
the WinXP machines - all but the WinXP Pro machine lose roughly 2% against
the wallclock somewhere and I have no idea what causes it - irritating...

This Barton machine is running at about 3600+ speed (ie. 11x200 for 2400MHz)
with all very fast disks including a dual 80GB WD Caviar SE RAID0 for video
capture alone yet ATI's MMC (MultiMediaCentre) takes up to 35% of the CPU
off SETI - a real resource hog..!

Ciao...

[UK]_Nick...