KISS - Prime95 with AMD XP1900
 

Hi, I have the following --
Athlon XP1900, 256mb dedicated, 24hrs per day, winders client.
Prime95 22.10 - Running Factoring
Is this the best I can do besides add more boxen? ;) :D

You have to add more boxen ;)

Well alrighty then...
I just added another AMD XP1800 boxen to Factoring. :D
Love your Avatar! :D

[b]IronBits[/b] wrote:
[quote]Is this the best I can do besides add more boxen? [/quote]

Yes, you can :exclaim:
You can OC your machines. I´ve an Athlon XP 1800+ that runs smoothly at 1667 MHz (same speed of a "regular" XP2000+). I guess you can do the same ;)

Just out of curiosity, why are you running factoring on a XP1900? Yes, there's an advantage over P4, but I'd think that you could really accomplish more doing 1st timers or even DC than factoring... Just curious. don't get defensive on me now...

... Sorry... double post. :surprised:ops:

Defense is for gauntlets :D
This is what I was told I should run with an AMD XP processor.
I have absolutely no clue as to what I'm doing with this client or this project.
I'm just trying all the clients/projects to learn more about them.
I'm all ears as I heard this project was only good for P4s, then I heard XPs kick butt on factoring.
So, I figured if I threw a couple boxen on factoring,
it could free up someone's P4 to move into the harder/longer to crunch stuff :)

It's a waste to run factoring on a Athlon XP, as a general rule.

They aren't as fast as P-IVs are per clock, but they're still plenty fast for doing LL tests with.

Just a clarification based upon my personal experience:

Up until version 22.7, AthlonXPs were much faster than P4s at trial factoring; my AXP 1900+ was about 80% faster than my 2.1 P4 (1.6 Northwood at 133 FSB).

The implementation of SSE2 for trial factoring in version 22.7 reversed that, and my P4 is significantly faster than the AXP. I am not sure of the difference, as I have yet to compare them directly.

Even though the P4 is faster, the Athlon is still more cost effective...

Here are some numbers to ponder...

http://arstechnica.infopop.net/OpenTopic/page?a=tpc&s=50009562&f=122097561&m=7670997135&r=7830993735#7830993735

I have an overclock question that kinda follows this thread I think.

If you overclock after you start a prime, your computer gives you a hardware error all the time because your actual mhz doesn't match your listed or benched mhz (or whatever). If I stopped the client, changed the mhz in my local.ini and restarted it would it update everthing? The first time it synced, Primenet should update too wouldn't it?

I was thinking that the client shouldn't care as long as the actual mhz is what's in the local.ini.

yup... I've done it. Just make sure you have P95 stopped while you change the .ini file 'cause otherwise it'll rewrite the file. When you restart the program it reads the P95 file again. And yes, it sends the updated clock speed to the server automatically.