20200323, 17:43  #12  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
2·3·11·67 Posts 
Quote:
https://www.mersenne.ca/mfaktc.php https://www.mersenne.ca/cudalucas.php 256.4/15.5 = ~16.5 You could get over 3 times the throughput in TF for less electricity cost with a GTX1650. 

20200323, 18:24  #13 
Mar 2020
Czechia, Tábor
2^{4} Posts 
These sites I'm already looking at. Time when I'll change my GPU is coming really fast.
Is here some way how to compare GPU and CPU performance? GPUs has GHz/day and CPUs ms/iter. Is here some way how to unify these units? One question regarding to worktodo.txt. When I have PC connected to PrimeNet and manually added some test. PrimeNet will send another work to that PC when it reaches setted cache? Or will it take into account the time needed for a manually added test and will not request additional test? @Uncwilly: Yes, I saw some double/triple test on found primes using GPUs. 
20200323, 19:52  #14  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
2×3×11×67 Posts 
Quote:
But ms/iter in P1 or primality testing changes faster than exponent does, due to the required fft length increasing. Computational effort per iteration in a primality test is ~p log p log log p; about p^{1.1}. Comparing GhzD/day, ms/iter, and hours run time, is sort of like comparing meters to hectares/minute and cubic kilometers. The relationships are taskdependent. The units are not dimensionally comparable. You might find the various posts linked in https://www.mersenneforum.org/showthread.php?t=24607 concerning "run time" helpful. Prime95 and mprime when PrimeNet connected will communicate expected completion dates for all items in the worktdo file to the server. More work will not be requested until what's queued for some worker falls below the threshold, which you can adjust. Last fiddled with by kriesel on 20200323 at 19:53 

20200323, 21:15  #15 
Mar 2020
Czechia, Tábor
16_{10} Posts 
From what I understand, CUDALucas can run LL test on GPU. I can run this also on CPU. How I'll figure out on which it will be faster or more efficient. Will it be better to do this test for example on GTX2080Ti or i99900. Or GTX260 () vs. Threadripper. This is what I'm trying to understand.
Thanks for that link. I'm going trough all of that, but its a looooot of informations... 
20200323, 22:28  #16 
Mar 2020
Czechia, Tábor
2^{4} Posts 
One more thing. Is here some way how to calculate how long it will take to my computer to do a test? In every calculator I found is again GHzdays, but CPU performance is in ms/iter. Should I use "P4 effective equivalent" written on my CPU page and when using 3 cores for one worker multiply that 3 times?
Ryzen 5 2600 has 3.823 GHz (3.392 GHz P4 effective equivalent) but old i52410M has 2.579 GHz (7.378 GHz P4 effective equivalent). New Ryzen has worst effectivity than P4 and almost 10 years old i5 from laptop is 2 times more effective than Ryzen So in case of Ryzen, 3,392 * 3 = 10,176GHzdays when running 24/7? If yes, what about CPU I'm using just for manual tests? In benchmark page is again ms/iter but that is not in GHzday unit.. 
20200323, 23:17  #17 
P90 years forever!
Aug 2002
Yeehaw, FL
23·311 Posts 

20200719, 05:17  #18 
Jul 2020
3 Posts 
Hello.
In the same line of the original question, I was looking in the Work Distribution Map and there are 244 exponents available to doublecheck in the 52M  53M range but as I try to get manual assignments at that range (Doublecheck LL/PRP tests) I get the error: Error code: 40 Error text: No assignment available meeting CPU, program code and work preference requirements Does anyone have a solution? Thanks. nemonusquam 
20200719, 08:10  #19 
"Alexander"
Nov 2008
The Alamo City
3·5^{3} Posts 
According to https://www.mersenne.org/thresholds/, exponents in that range (Cats 01) are not available for manual testing.

20200719, 14:32  #20  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
2×3×11×67 Posts 
Quote:
Set your manual assignment requests to get lowest exponents' DC below 57885161. That will contribute to softening up the 55M, 56M, or 57M range in advance. If enough of us hit LL DC hard we may DC everything below M57885161 within a year. https://www.mersenne.org/report_milestones/ says 61,525 DC to go. That's an average of less than one per month per active GIMPS participant. https://www.mersenne.org/thresholds/ shows that above ~57.3M is cat 4 territory currently, so everyone can help. Last fiddled with by kriesel on 20200719 at 14:35 

20200719, 16:23  #21  
6809 > 6502
"""""""""""""""""""
Aug 2003
101×103 Posts
8606_{10} Posts 
Quote:
Quote:


20200721, 16:18  #22  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
2·3·11·67 Posts 
Quote:
x ms /iter x p iterations / 1000 / 3600 / 24 = n days per exponent. At https://www.mersenne.ca/credit.php for the same p, select LL test, get GhzD/exponent. Divide GhzD/exponent / days/exponent to get GhzD/day for your cpu worker. Then you can use that figure to roughly estimate the time to complete any p, with a scaling according to about p^{2.1}. For example, if your cpu takes 2. weeks to do a 111M primality test, expect about 2 x (332/111)^{2.1} = 20. weeks for a 332M exponent (100Mdigit) Run time scaling and much more is covered at https://mersenneforum.org/showthread.php?t=24607 Last fiddled with by kriesel on 20200721 at 16:19 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Best type of work for lowest exponent work?  cappy95833  Software  5  20191121 04:24 
how to get cudaLucas work for large exponent?  fairsky  GPU Computing  5  20131122 10:33 
Illchosen password restrictions  James Heinrich  Puzzles  42  20111124 16:03 
Different B1 & B2 values chosen on P1 resume  azhad  Software  0  20061230 06:36 
I've chosen primality test task, but info shows P1 factoring! Why ?  Unregistered  Software  3  20040223 16:45 