Subject: | |
From: | |
Reply To: | |
Date: | Thu, 5 Aug 1999 12:09:06 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Gavin Scott wrote:
>
> Terry queries:
> > OK, I want to know what Mark and Gavin are running their Seti software on?
> > They are reporting average runtimes of 9hr 37min and 11hr 41min respectively.
>
> HP9000 K420 (mostly full time) and Dell 400Mhz PII running Linux (at
> night, weekends). Both are almost exactly the same speed at ~10 hours
> per work unit. The K420 has two CPUs and runs two instances of the
> SETI client, so the box produces two results per 10 hours on average.
>
> > They are so much faster than everyone else, it's not funny.
>
> Basically the Windows version of the client is terrible (or at least the
> older ones were, I haven't run the recent ones). The Dell PC is around
> four times faster running the non-gui Linux SETI client than it is running
> the Windows version.
My home Gateway 400Mhz PII 128MB Win98 machine runs the GUI client full time
and completes work units in about 11 hours.
It's on my to-do list to get the Linux client running on my other home machine,
a 350Mhz PII 64MB. My home machines have an always-on DSL connection, so no
time is lost waiting for modem permission to do the work unit upload/download.
AFAIK, CCCD is still doing SETI work on my behalf, using my desktop Win95
266Mhz PC, and both processors of a dual-processor 9000/V2250 with 2GB of RAM
that would otherwise be sitting mostly idle. I expect those machines to
eventually stop searching, so Gavin will possibly surpass my totals someday.
> We also had a head start on most people.
I started just a couple of days after the beta period ended.
> > Also, there was talk at one time of an MPE port of the Seti client,
> > anyone pursuing this idea?
>
> I believe multiple people have emailed them, but nobody has gotten a
> response.
No response here either.
- Mark B.
|
|
|