Comment Re:Another AMD user.... (Score 1) 257
> I run on a 450 MHz AMD-K6-2,
> with the 3d-now! extensions (of course). I can
> tell you from experience that the FFT that
> Seti@Home uses routine on an AMD SUCKS. It takes
> forever to do a single block of data, and I
> calculated it would eventually take something
> like 70 hours to complete the block. I was
> disappointed.
Wow, 70 hours? I'm running SETI@Home on Linux with an AMD K6-2 450, and according to my handy tk-SETI@Home client, I am averaging 14 hours 55 minutes. Granted, that's not great, but it's not 70 hours, either. 'Course, it may have something to do with my Super7 100 MHz bus and 128 MB RAM, though I am pretty much in the dark as to how the client uses resources... Anyway, I just thought I'd throw in my .02 regarding performance.
-Chris
> with the 3d-now! extensions (of course). I can
> tell you from experience that the FFT that
> Seti@Home uses routine on an AMD SUCKS. It takes
> forever to do a single block of data, and I
> calculated it would eventually take something
> like 70 hours to complete the block. I was
> disappointed.
Wow, 70 hours? I'm running SETI@Home on Linux with an AMD K6-2 450, and according to my handy tk-SETI@Home client, I am averaging 14 hours 55 minutes. Granted, that's not great, but it's not 70 hours, either. 'Course, it may have something to do with my Super7 100 MHz bus and 128 MB RAM, though I am pretty much in the dark as to how the client uses resources... Anyway, I just thought I'd throw in my
-Chris
