![]() |
![]() |
#1 |
"Luke Richards"
Jan 2018
Birmingham, UK
25·32 Posts |
![]()
Hi,
I have a computer that is only ever on occasionally, but when it is on it's usually on for a good few hours (say 3-6 hours) at a time. It has access to 16 cores and I've set P95 to run 16 workers running TF on each. Worker 1 collects a TF job, but PrimeNet is assigning LL DC work. Is there any way to override this? Worker 1 had 14 jobs queued up so for now I've gone into worktodo.txt and reallocated 13 of them manually to workers 2-14, but P95 has just appended the LL DC job to do after that TF is done. I don't want to do LL work on here - a job takes far too long on a computer that is only running for, say, 12-24 hours a month. |
![]() |
![]() |
![]() |
#2 |
Einyen
Dec 2003
Denmark
7×433 Posts |
![]()
Probably because that computer never did a DC and your account is set to "one matching double-check yearly" for each computer:
https://www.mersenne.org/thresholds/ |
![]() |
![]() |
![]() |
#3 |
"Luke Richards"
Jan 2018
Birmingham, UK
25×32 Posts |
![]()
Update:
I logged into my mersenne.org account and found that Workers 2-14 were set for "Whatever makes most sense", despite that not being the setting in Prime95. Having manually changed each core on mersenne.org to be doing TF work, closed P95 and reopened it, we're now up and running as expected. |
![]() |
![]() |
![]() |
#4 |
Sep 2009
3·23·29 Posts |
![]()
TF on a CPU is not much use since GPUs do TF much faster than CPUs do. Has it got enough RAM to do P-1 tests? That would be more use to the project.
Chris |
![]() |
![]() |
![]() |
#5 |
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
4,903 Posts |
![]()
How many TF GhzD/day can the cpu in question provide? A good gpu can do 1000 to 3000, 24/7. (GTX1080, 1650 are ~1000; RTX2080 Super ~3300. The best use of a cpu core for TF is to keep a good gpu well fed, or several. https://www.mersenne.ca/mfaktc.php https://www.mersenne.ca/throughput.p...2288&mhz2=2700)
I'll occasionally run cpu TF, but only for test purposes, or the very rare foray into very high exponents that available gpu software like mfaktx can't handle. |
![]() |
![]() |