Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Project Staging Area :
master_prpclient.ini settings
Author |
Message |
|
I haven't done PSA for a long time (want to finally get off my bronze badge) and need a bit of help setting it up.
I've got a GTX590 (dual GPU) and only want to do GPU work, no CPU.
What server and executable do I need to add or remove the "//" from in master_prpclient?
Also the <pct> and <workunits> or any other settings.
Does the userid need PG after it (userid=PG_myusername) or just userid=myusername ?
I'm running Windows 7, 64 bit.
Thanks
| |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13804 ID: 53948 Credit: 345,369,032 RAC: 1,967
                              
|
I've got a GTX590 (dual GPU) and only want to do GPU work, no CPU.
Comment out the CPU (and 32 bit GPU) versions of WWWW, leaving only the 64 bit GPU program:
//wwwwexe=wwww.exe
//wwwwexe=wwwwcl.exe
wwwwexe=wwwwcl64.exe
What server and executable do I need to add or remove the "//" from in master_prpclient?
Also the <pct> and <workunits> or any other settings.
You'll want to run WALLSUNSUN and/or WIEFERICH. Those are the two PRPNet projects that currently use GPUs.
PCT should be 100 (or 50 if you run both), and workunits should be 10 to 20.
You WILL want to set up an ini file to optimize the GPU settings -- the defaults result in very slow performance. I'd recommend reading this thread which should have a discussion about how to set it up.
You will want to set this up as "dual core", with two separate instances, each in its own directory. One instance for each GPU.
Does the userid need PG after it (userid=PG_myusername) or just userid=myusername ?
Don't use "PG".
userid=David_Steel
Note the "_" between the words because PRPNet won't allow a space inside a username.
If you prefer, you could also do manual sieving rather than PRPNet. We're currently doing PPR, GFN and Cyclo sieving on GPUs.
____________
My lucky number is 75898524288+1 | |
|
|
That thread said Wieferich and Wall-Sun-Sun are the only ones that need the ini file.
I wouldn't know how or where it goes, prefer to keep it simple.
What about Genefer?
Thanks | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13804 ID: 53948 Credit: 345,369,032 RAC: 1,967
                              
|
That thread said Wieferich and Wall-Sun-Sun are the only ones that need the ini file.
I wouldn't know how or where it goes, prefer to keep it simple.
What about Genefer?
Thanks
That thread should have a description in there of how to set up the ini file.
All of the PRPNet Genefer ports are either well beyond the limits of the GPU programs, or are at the very edge and will switch to using the CPU on most if not all tasks.
Currently, if you want to use a GPU to get PSA credits, your choices are WSS, WIEF, or manual sieving.
If you're not in a hurry, you can wait until we get Cyclo running, but I can't guess how long that will be. It could be weeks, months, or never. Cyclo is similar to Genefer, and the current plan is to get it running on PRPNet.
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13804 ID: 53948 Credit: 345,369,032 RAC: 1,967
                              
|
You need to create a file called "wwww.ini" in each PRPNet instance directory.
Here's the template for that file:
// The settings in this file are used to set various values that cannot be set via command line
// switches. Except where noted, the command line switches will override values specified here.
// platform and device specify the platform and device to run on
//platform=0
//device=0
// blocks is a multiplier used to set workgroup size
//blocks=1000
// threads is the number of concurrent threads to execute
//threads=2
// minprime and maxprime set the range to be searched
//minprime=
//maxprime=
// These settings will override the default settings for blocks and threads and they will
// also override the command line switches
//wallsunsun_threads=5
//wallsunsun_blocks=4000
//wieferich_threads=2
//wieferich_blocks=3000
This is what I personally use:
platform=1
threads=4
blocks=3000
Oh, one more thing, since you have two GPUs. You'll need to set "gpuaffinity=" to a different value in each of the two prpclient.ini files in the instance directories. I believe the values should be 0 and 1, but I'm not certain (I've never used dual GPUs.) That will tell each instance which GPU to use.
There's a "device=" in wwww.ini and a gpuaffinity in prpclient.ini. I'm not sure which one takes precedence here. My guess would be the setting in wwww.ini.
EDIT: Ignore my comments about the "gpuaffinity=" setting. It seems they don't apply to WWWW. Use "device=" in wwww.ini instead.
____________
My lucky number is 75898524288+1 | |
|
|
Ok thanks I will give it a go.
I'll also look into the manual sieving, is that any easier to get set up and running? | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13804 ID: 53948 Credit: 345,369,032 RAC: 1,967
                              
|
Ok thanks I will give it a go.
I'll also look into the manual sieving, is that any easier to get set up and running?
It depends on what you mean by easy. If creating text files or using DOS window commands is "difficult", you might want to stick with BOINC. If working with text files and command lines isn't a problem, then the only "difficult" part is learning about the config files, and this is a one time event. Once you set it up, it will run on its own.
Manual sieving is a bit more involved and it requires more hands-on effort being as it's, you know, manual. You manually select a range to sieve, run the sieving software on your own, upload the results to the server by hand, and report the completed range by hand. Nothing's particularly difficult to do, but you're doing everything by hand. In one sense manual sieving is "easier" because it's less automated and less to configure. But it's also more "difficult" because more effort is required to do it.
Put another way, PRPNet is analogous to a smartphone and manual sieving is a flip phone. Which one is more difficult to use depends on your point of view.
____________
My lucky number is 75898524288+1 | |
|
Scott Brown Volunteer moderator Project administrator Volunteer tester Project scientist
 Send message
Joined: 17 Oct 05 Posts: 2329 ID: 1178 Credit: 15,638,371,047 RAC: 10,116,889
                                           
|
"gpuaffinity" has no effect on WSS or WFS work. You must use the "device" setting in the wwww.ini file.
I also tend to use the
// These settings will override the default settings for blocks and threads and they will
// also override the command line switches
//wallsunsun_threads=5
//wallsunsun_blocks=4000
//wieferich_threads=2
//wieferich_blocks=3000
section uncommented because the performance (and screen lag) varies (sometimes considerably) between WFS and WSS work, even on the same GPU. You will need to tinker with these settings to get the best performance from your specific GPUs.
| |
|
|
Ok, please treat me like a noob (if you are not already), I seriously don't know how I got PSA to run in the past...
When I unzipped the 5.3.2 package, it created 9 folders (programs and prpclient 1 to 8) plus all the other stuff below them - batch files and text docs etc...
There is a wwww.ini there and also one in the programs folder.
Do I need to change one or both wwww.ini and do I need to then put a copy in each prpclient folder (8 of them)?
I also hope I chose the right install in the first place LOL... (8-oct-install-prpclient) or are you saying I should install the 2-dual?
And back to the master_prpclient.ini, the default settings have "//" removed from the following:
server=27:0:1:prpnet.primegrid.com:12006
llrexe=llr.exe
pfgwexe=pfgw32.exe
geneferexe=genefer32.exe
So do I add // to them and remove from the following and that's it?
//server=WIEFERICH:0:1:prpnet.primegrid.com:13000
//server=WALLSUNSUN:0:1:prpnet.primegrid.com:13001
//wwwwexe=wwwwcl64.exe
Thanks, again | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13804 ID: 53948 Credit: 345,369,032 RAC: 1,967
                              
|
When I unzipped the 5.3.2 package, it created 9 folders (programs and prpclient 1 to 8) plus all the other stuff below them - batch files and text docs etc...
There is a wwww.ini there and also one in the programs folder.
Do I need to change one or both wwww.ini and do I need to then put a copy in each prpclient folder (8 of them)?
ONLY the files in the instance directories (the prpclient directories) matter. Those are the ones that are run. You need ot create a wwww.ini in each prpclient directory. Remember they need different "device=" settings.
The only exception is master_prpclient.ini in the top directory, which is there for convenience. You can modify master_prpclient.ini, run one of the setup scripts (-oct- since you created 8 direcotires) and the setup script copies the contents of the master ini file into the prpclient.ini (Note no "master_") in each of the prpclient directories.
It's the prpclient.ini files in each prpclient directory that actually determines what prpclient does.
I also hope I chose the right install in the first place LOL... (8-oct-install-prpclient) or are you saying I should install the 2-dual?
As long as you have ENOUGH directories, it's ok. You need one directory for each CPU or GPU you're going to run simulataneously. Since you don't know what you're going to do in the future, it's wise create a directory for each core PLUS each GPU in case you ever want to run them all at once. For your immediate plans, two is sufficient, but more doesn't hurt. When you START it, just start the number of instances you're actually running.
And back to the master_prpclient.ini, the default settings have "//" removed from the following:
server=27:0:1:prpnet.primegrid.com:12006
llrexe=llr.exe
pfgwexe=pfgw32.exe
geneferexe=genefer32.exe
So do I add // to them and remove from the following and that's it?
//server=WIEFERICH:0:1:prpnet.primegrid.com:13000
//server=WALLSUNSUN:0:1:prpnet.primegrid.com:13001
//wwwwexe=wwwwcl64.exe
Do this:
//server=27:0:1:prpnet.primegrid.com:12006
llrexe=llr.exe
pfgwexe=pfgw32.exe
geneferexe=genefer32.exe
server=WIEFERICH:50:20:prpnet.primegrid.com:13000
server=WALLSUNSUN:50:20:prpnet.primegrid.com:13001
wwwwexe=wwwwcl64.exe
(Or only one of the two servers, if you prefer.)
____________
My lucky number is 75898524288+1 | |
|
|
There are specific folders prpclient-1 through prpclient-8 so that you can run up to eight instances of the PRPNet client at the same time. The files actually used are the ones inside these folders.
When you ran the 8-oct-install, all these eight .ini files were copied out there into the distinct folders from the "original" in the parent folder. You can modify the .ini files in some of the subfolders, and leave them unchanged in others. For example you could use one GPU in prpclient-1 and prpclient-2, another GPU in prpclient-3 and prpclient-4, and your quad-core CPU in prpclient-5 through prpclient-8.
Remember to edit both prpclient.ini and wwww.ini in all these numbered subfolders. (wwww.ini is not important in folders where you plan to use only CPU.)
You could use 8-oct-update to overwrite the settings in all eight folders with what is in the "original" in the parent folder.
You use 8-oct-start to start all eight instances of the client. If you want to start only prpclient-1 and prpclient-2, for example, use 2-dual-start, etc.
If the machine has a dual-core GPU, no other GPUs, and you do not want to do CPU work, it sounds like you need only prpclient-1 and prpclient-2.
/JeppeSN | |
|
|
Ok so I got it going but it needs some tweaking...
My GPU's are only running at about 45% but CPU usage is at 65%.
How can I get the GPU in the 90's and CPU right down?
I'm sure its a setting I've missed!
Also, is the machineid= the 6 digit ID number of one of my PCs in 'Computers on this account'?
Thanks
wwwwcl v2.2.5, a GPU program to search for Wieferich and WallSunSun primes
Sieve started: (cmdline) 425819400000000000 <= p < 425819500000000000
p=425819425286059429, 20.53M p/sec, 2.18 CPU cores, 25.3% done. ETA 19 Feb 16:51
Sieve complete: 425819400000000001 <= p < 425819500000000000 2463483775 primes tested
Clock time: 122.06 seconds at at 20182733 p/sec.
Processor time: 264.75 sec. (3.82 init + 260.93 sieve).
Seconds spent in CPU and GPU: 8.42 (cpu), 62.07 (gpu)
Percent of time spent in CPU vs. GPU: 11.95 (cpu), 88.05 (gpu)
CPU/GPU utilization: 2.17 (cores), 0.51 (devices)
[2015-02-19 16:49:52 AEDT] WIEFERICH: Range 425819400000000000 to 425819500000000000 completed
| |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13804 ID: 53948 Credit: 345,369,032 RAC: 1,967
                              
|
Also, is the machineid= the 6 digit ID number of one of my PCs in 'Computers on this account'?
Machine ID can be whatever you want. It has no relationship to the BOINC host IDs. Many people simply use whatever name they call the computers on their home network.
As for your other questions, I can't help you with tuning the settings, sorry.
____________
My lucky number is 75898524288+1 | |
|
|
WALLSUNSUN are running at 90-95% GPU but WIEFERICH are only 45%.
Does anyone know how to get wieferich up to 90% or how to run 2 work units at once?
Thanks
| |
|
GDBSend message
Joined: 15 Nov 11 Posts: 280 ID: 119185 Credit: 3,418,510,355 RAC: 3,874,525
                      
|
Have you copied wwww.ini into instanst directory, and uncommented wieferich_threads and
wieferich_blocks? | |
|
|
WALLSUNSUN are running at 90-95% GPU but WIEFERICH are only 45%.
Does anyone know how to get wieferich up to 90% or how to run 2 work units at once?
Thanks
It's easy enough to run two instances at once just by running them out of two different prpclient-N folders. Set the "device=" value in wwww.ini to the same value (0, if you have only one gpu).
If you just want to run out of one folder, experiment with the settings GDB just mentioned (prior post).
--Gary | |
|
Message boards :
Project Staging Area :
master_prpclient.ini settings |