>
>
> FYI - I ran some benchmarks using TeamLambChops SetiAtHome benchmark file
> and was rather disappointed. I have two Celeron 366's OCed to 550 (100Mhz
> FSB) and found the following under Redhat Linux 6.1 using the 2.4 CLI
> client:
>
Yeah, well I just dumped the Abit Bp6 for good today. I stopped using it as my
main machine
about 2 weeks ago, and replaced it with a bxmaster coppermine 750e o/c to 840.
Anyway,
I converted the Bp6 dual 500 into a firewall/seti cruncher and the piece of
shit would continue
to lock up under the strain of seti-packets. It would take 14+ hours if both
procs were running
seti packets and 10 hours 45 mins if one proc was active. I know the seti
packet from
lamb chops is a little weak (the packet is not a true representation of the
average seti packet),
but it does server the purpose you used it for.
Since I have replaced the abit Bp6 with a single 500 o/c to 563 (and placed the
Bp6 in the trash),
it has taken over 2 and half hours off my crunch times.
The bp6 was a good idea, but its a piece of shit and SMP is a *FUCKING JOKE*
with a 66mhz
FSB.
>
> (1) SetiAtHome finishes in 6 hours, 51 minutes (not bad)
> (2) SetiAtHome's finish in 10 hours, 3 minutes (a 3 hour, 12 minute slowdown
> per instance)
>
> That implies to me about a 50% contention for memory between the two
> processors.
>
> Kevin C.
>
> --
> =- To unsubscribe, email [EMAIL PROTECTED] with the -=
> =- body of "unsubscribe linux-abit". -=
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=- body of "unsubscribe linux-abit". -=
