Christian Schulz wrote: > On Mon, Nov 03, 2008 at 04:51:07PM +0000, Steve Rogerson wrote: > > >> Hi, I was using V24 on my dual core linux box running two copies. With >> V25 it looks as though it does this automatically, ie one invocation >> brings up two threads(?). The problem is that the 1st Worker picked one >> of the previous runs but the 2nd worker assigned a new one and ignored >> the previous. How can I get back to the original prime candidate now in >> limbo about 50% through. >> > > My guess is to change settings in local.txt; there are parameters > "WorkerThreads=n" and "ThreadsPerTest=k". In your case it should be > n=2 and k=1. I'd try to re-set it with n=1 and k=2 which will give two > threads working on the same exponent. > Only do this if you wish to slow down your overall rate of result production. Running separate single thread per test is still more efficient.
It will somewhat speed up the rate for individual tests at the expense of wasting extra overhead slowing your overall production. For example if you turn out a LL test (of a certain size) every 20 days on each of 2 cores and change over to 2 threads per test It might put out one LL test every 13 days, thus taking 26 days to do 2 tests instead of 20 days. The exact numbers will vary for various CPU types and test sizes but the result will be the same. _______________________________________________ Prime mailing list [email protected] http://hogranch.com/mailman/listinfo/prime
