-   Factoring (
-   -   Benchmarking problem with Prime95 (

jasong 2006-03-22 19:30

Benchmarking problem with Prime95
Guys, I have no idea what I'm doing wrong.

I'm attempting to set up benchmark tests for my Sempron using what I was told were optimal values. But each test I've done, from 15-digit to 45-digit takes less than .001 seconds.

I'm using the menu feature obtained with the password and going to ecm. My exponent is 1009, I use the values I got off the web, and I set it for one curve. I'm not totally sure what files I could post so I'm not going to post anything.

I'm probably leaving out key info, but I'm not sure what else to do.

Uncwilly 2006-03-22 20:41

Go to the menu. Stop the current test (TEST->STOP) . Then go to Benchmark (OPTIONS->BENCHMARK). The current version of the program will bench factoring.

I don't know the exact numbers, but what you said about 45 (bits? maybe) in that short of time sounds right.

jasong 2006-03-22 21:24

Thanks a lot. I didn't realize that was a feature.

jasong 2006-03-22 21:31

I got the following results:
[code]AMD Athlon(tm) XP 2200+
CPU speed: 1747.55 MHz
CPU features: RDTSC, CMOV, Prefetch, 3DNow!, MMX, SSE
L1 cache size: 64 KB
L2 cache size: 256 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 256
Prime95 32-bit version 24.14, RdtscTiming=1
Best time for 58 bit trial factors: 7.059 ms.
Best time for 59 bit trial factors: 7.062 ms.
Best time for 60 bit trial factors: 7.052 ms.
Best time for 61 bit trial factors: 7.098 ms.
Best time for 62 bit trial factors: 12.577 ms.
Best time for 63 bit trial factors: 12.616 ms.
Best time for 64 bit trial factors: 30.573 ms.
Best time for 65 bit trial factors: 31.097 ms.
Best time for 66 bit trial factors: 31.988 ms.
Best time for 67 bit trial factors: 31.865 ms.[/code]
While I know what a millisecond is, I'm not sure how to apply this information to "curves." Does knowing the exponent is 1009 help, and if so, how?

Mystwalker 2006-03-22 21:51

Unfortunately, the benchmarking doesn't feature P-1/ECM tests, but only TF and LL testing.

You can set Options --> Preferences... --> Iterations between screen outputs to 999999999 to avoid all those intermediate outputs. You can then see how much time each curve took.

jasong 2006-03-22 23:10

Guys, I don't know what's going on, but it absolutely refuses to do Stage 2 ecm. And the results.txt file is printing some sort of alphanumeric junk.

jasong 2006-03-23 05:12

Never mind, I decided to edit the worktodo file directly.

Had a second problem which made me swear a little. TivoTransfer was using up all the cpu it could get it's greedy hands on even though it wasn't supposed to be doing anything at the time.

Never assume you know what's going on in your computer. Every time I think I've learned that, something happens to prove I haven't.

All times are UTC. The time now is 10:08.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.