[iPad]

I have a Yosemite G3/300 with 512K of cache, and i'm getting a WU done on average in 13 hours. WHY?

I've done everything, quit finder, lauch peekaboo while launching SETI@Home as an application and then doing hotkey for screensaver and 1 min blank screen, turned virtual memory off, and overclocked my cache. What am I doing wrong? What is the best possible setting?!

------------------
People aren't as dumb as you think. Wait, what was I thinking, 90% of the world uses WINDOWS!
You don't like Macs? Good, more for me.

[Misha]

Get a faster computer

Your scores are on par with what a G3/300/512k should produce...

[pcurtner]

G4s are just that fast on SETI-- my G3s are all in the 12-16 hr range, my G4s are all in the 4-6 hr range.

As for WUs, the stats can be misleading, since some of us are running many more than 1 computer.

[wlonh]

a beige rev2 G3 minitower with a 466MHz/1M L2 yields (approx) 5.5 to 6.5 hour WU's depending on the WU...

very respectable and a big reason why i remain very happy with my 'old' (ha) beige with OldWorld ROM... i will be droppping another ZIF into it in a few months, whenever the MHz numbers get too tempting...

pardon me but my beige rox, have not been tempted by the G4 yet... boost that bus speed some more along with higher CPU speeds, and give me more altivec apps and i will buy G4... looks like late this year or early next year to me... because even if Apple puts out a model next week (not likely, nor is it rumored though it may be, i don't care for rumors... show me the money!! ) with a higher bus speed and CPU speeds, i will wait for rev2 or rev3 of it... word to your mother!!

my rev2 beige G3 minitower is troublefree, whatta machine

[iPad]

But I seriously think there is something wrong with my computer because my dad's beige G3/266 does a WU in 13 hours 5 min while my Yosemite G3 does it in 13 hours 26 min.

The Yosemite G3/350 does a WU in 9-10 hours. Even though it has 1MB of L2 Cache and a 50Mhz higher clock speed (G3/300 has 512K), it shouldn't really result in a 3 1/2 hour difference. What am I doing wrong?

------------------
People aren't as dumb as you think. Wait, what was I thinking, 90% of the world uses WINDOWS!
You don't like Macs? Good, more for me.

Clock speed is not the only factor you need to consider. How much and how fast the RAM you have is also a big factor. The RAM bus is where most of SETIs FPU processing is done. I have a B&W 400 with 768MB RAM,dual 9GB UW SCSI HD. That machine can process a work unit in less than 7 hours. I have the machine configured with AppleTalk off, Multiple Users off, libmoto extension installed and RAM disk twek.

FireWire

[iPad]

I have already taken these factors into action. My computer has the same amount of RAM, but faster, my computer has a larger much faster hard drive, my computer has a faster system bus, my computer has been modified with many applications to make it faster while my dad's computer has only peekaboo. Everything. Previously when i didn't have all those things, my Yosemite would process WU in 14 and a half hours.



------------------
People aren't as dumb as you think. Wait, what was I thinking, 90% of the world uses WINDOWS!
You don't like Macs? Good, more for me.

[pcurtner]

Have you tried your 'slower' machine without all of those extra extensions, CPs, Kaleidascope/Kineticon-type stuff?

'Many applications to make it faster' seems like it would cause problems with something like SETI-- try running it with a minimal extension set and see if your scores improve.

[Todd Madson]

This is what I do to get my low 5 hour times:

My machine is a Sawtooth G4 / 400 with 128 megs of ram.

Times range on the low end from about 5 hrs 8 mins to around 5 hrs 11 mins avg. to low sixes.)

(1) appletalk is off.
(2) virtual memory is off.
(3) Seti app is windowshaded.
(4) screen saver set to activate in 1 minute
(5) screen set to blank in one minute
(6) PowerLogix Cache Control 1.3 sets L2 cache to 267.5 mhz from 199 mhz.
(7) use Peek-a-Boo to stop all other processes, even the finder. Just Seti.
(8) make sure the disk indexing scheduler isn't running - big cpu sucker, goes for eons.
(9) set screen to thousands of colors instead of millions or 256.
(10) set resolution to medium, not high.
(11) you could run the app in a ramdisk to avoid disk access.
(12) that's all I can think of.