CPU Assignments aren't working

Dubslow · 2011-07-25, 04:45

Hey guys,
This is Linux M/Prime/95 dual booting from the same folder as Windows, hence the program name given. I don't know about Windows, but in Linux, when I choose menu option 2, Test/Worker threads, and set the workers to use a specific cpu, whenever I close the menu and come back, it always has reset to smart cpu assignment. I think this makes a difference, because when I run Worker 1 LL and the rest factoring, I get .060-.065 seconds per iteration. When I have 1 and 2 do LL and the rest factoring, 1 jumps to .070-.075 seconds per iteration, while 2 is the same .060-.065 as before. I can only think of this being a result of the cpu assignments, but like I said, they won't stick. Is there some way to manually edit local.txt or prime.txt to assign workers to cpu's? That would have the added benefit of also maintaining the same assignments in Windows.

AMD Phenom II X6 1055 Thuban 2.8 GHz Six core Processor
8 GB RAM
Ubuntu 11.04
Windows 7 (Professional?)

And see here on the differences between OS's:
http://mersenneforum.org/showthread.php?t=15771

Dubslow · 2011-07-25, 05:00

Got it, nvm. Turns out stopping the worker threads while changing the preferences helps. Also found the relevant place in the local.txt file. The one thing to note is that in the file the cpu's are numbered from 0, not 1, even though in the output they are numbered from 1. Someone please delete this thread.

2011-07-25, 04:45	#1
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 1C35₁₆ Posts	CPU Assignments aren't working Hey guys, This is Linux M/Prime/95 dual booting from the same folder as Windows, hence the program name given. I don't know about Windows, but in Linux, when I choose menu option 2, Test/Worker threads, and set the workers to use a specific cpu, whenever I close the menu and come back, it always has reset to smart cpu assignment. I think this makes a difference, because when I run Worker 1 LL and the rest factoring, I get .060-.065 seconds per iteration. When I have 1 and 2 do LL and the rest factoring, 1 jumps to .070-.075 seconds per iteration, while 2 is the same .060-.065 as before. I can only think of this being a result of the cpu assignments, but like I said, they won't stick. Is there some way to manually edit local.txt or prime.txt to assign workers to cpu's? That would have the added benefit of also maintaining the same assignments in Windows. AMD Phenom II X6 1055 Thuban 2.8 GHz Six core Processor 8 GB RAM Ubuntu 11.04 Windows 7 (Professional?) And see here on the differences between OS's: http://mersenneforum.org/showthread.php?t=15771 Last fiddled with by Dubslow on 2011-07-25 at 04:51 Reason: adding link

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Why aren't you a murderer?	Zeta-Flux	Soap Box	58	2008-06-07 19:15
Autistics aren't handicapped, just misunderstood	jasong	Soap Box	13	2008-03-11 22:03
Aren't we done this range?	petrw1	PrimeNet	1	2007-07-25 14:48
aren't self tests one-time only?	ixfd64	Software	1	2006-04-24 00:04
There aren't enough black holes!	Fusion_power	Soap Box	3	2005-05-22 20:00

2011-07-25, 05:00	#2
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3×29×83 Posts	Got it, nvm. Turns out stopping the worker threads while changing the preferences helps. Also found the relevant place in the local.txt file. The one thing to note is that in the file the cpu's are numbered from 0, not 1, even though in the output they are numbered from 1. Someone please delete this thread.