Prime 95 24hr Stability Test - Screen Shots
Prime 95 24hr Stability Test - If you can do it Post a screenie!
Mobo: EPoX 9NDA3+ v2.1
CPU: Winchester 3200+ 2.5ghz v1.55
Memory: G Skill TCCD 1GB "LE"
Heatsink: Stock AMD Athlon 64 Copper Bottom Heatsink w AS Ceramique
PSU: Generic 600w 12v@20A, 5v@40A 3.3v@30A
Not the greatest OC but it's STABLE
DURATION: 29hrs 58mins 57 seconds
Mobo: EPoX 9NDA3+ v2.1
CPU: Winchester 3200+ 2.5ghz v1.55
Memory: G Skill TCCD 1GB "LE"
Heatsink: Stock AMD Athlon 64 Copper Bottom Heatsink w AS Ceramique
PSU: Generic 600w 12v@20A, 5v@40A 3.3v@30A
Not the greatest OC but it's STABLE
DURATION: 29hrs 58mins 57 seconds
0
Comments
CPU: Winchester 3000+ 2.3ghz v1.55
Memory: G Skill TCCD 1GB "LE"
Heatsink: Stock AMD Athlon 64 Copper Bottom Heatsink w AS Ceramique
PSU: Generic 600w 12v@20A, 5v@40A 3.3v@30A
Not the greatest OC but it's STABLE
DURATION: 25hrs 43mins 26 seconds
It's a Crawl, Walk then Run thing
Then post.....Why am I losing WUs, my MP3 player and Browser run just fine....
Those who Can Do, Those who Cant, claim it doesn't matter.....
The torture test compares the results you get from a FFT to a known result to check for errors and stability problems.
You're fired.
edit:
and 1 is not prime either.
and the prime numbers that prime95 is trying to factor are huge - the most recent one found is 2^(25,964,951) -1, which has more than 7,000,000 digits.
edit:
You're still fired.
edit2:
This brings up a good point though. It's easy to tell whether or not a smaller integer is composite or prime, as you can just try to divide it by all the integers up to 1/2 the number. However, once you get bigger, it's really hard to tell if an integer is composite (provided the integer is odd): 836381, for example. I know it's composite because I made it by multiplying prime numbers, but you really can't tell just by looking at it. And that's only a 6 digit number. It takes too long of a time for a computer to determine if a very large number is prime or composite using division by smaller numbers, so there are assorted algorithms used to determine primality.
No, no table. It goes thru every number and finds if it as a prime number by dividing and using the % operator. You could enter 1,000,000,000,000,000... if you wanted to but it will take while. About 2.5 min for 40,000 on my 1.6 P-M.
LUT = Look Up Table
I hope you're only going up to i=x/2 for x%i - otherwise you're just doing wasted calculations :-P
@checkmate
I don't have it out for you in particular - I would have done the same for anyone else.
EDIT: Is this number Prime? 17859815757571764576471457645161
While there are an infinite number of both prime and composite numbers, for a large finite number (Let's say it's your number, plus 1), there are more composite numbers than prime numbers between it and zero. And if I say it isn't, then you have to prove me wrong by dividing the number by every number up to half the number (or prove me right by doing so); whereas if I say it is prime, you only have to find a number that divides it. Also, I assume you're going to ask a question you know the answer to, so I assume you created it by multiplying primes to form a composite number.
EDIT:
And it's not prime because if you sum all the digits, you get a number which is divisible by 3, which means the number itself is divisible by 3
The purpose of the lab was to make 3 max threads in XP running at the same time. Once one was done the user could enter another if desired if not then the program would wait for all threads to complete before exiting. The purpose was not to get a good/correct algorithm (in fact he signed off on the lab with all kinds of results) but rather the threading execution in Windows.
If you don't mind using some memory, if you store primes you found previously in an array, you can speed it up a lot, as you don't need to check to see if a number is divisible by composities, only by primes to see if it is prime.
for fun with threads, try running this one:
while(fork() || !fork()){