PrimeGrid: PRPNet September Challenge
Factorial Equinox
Challenge

The equinoxes are the only times when the solar terminator (the "edge" between night and day) is perpendicular to the equator.
As a result, the northern and southern hemispheres are equally illuminated.
The Latinate names vernal equinox (spring) and autumnal equinox (fall) are often used.
To celebrate we're running a PRPNet challenge at the FPS (factorial prime search) from 22nd 18:00 UTC until 27th of September 18:00 UTC.
 
To take part, you have to activate the following line in prpclient.ini:
server=FPS:100:1:prpnet.primegrid.com:12002
Stats will be available at the well known place here .
All previous PRPNet challenge stats can be found here .
Discussion and more information can be found here: 2017 PRPNet September Challenge.
 
Files are the same as last event, that is the same version and date stamp.
Downloads: http://prpnet.primegrid.com/
7-Zip Tool
Windows: http://www.7-zip.org/
Linux, Mac: http://sourceforge.net/projects/p7zip/files/
 
Good luck! 9/22/2017 14:12:15 · more...
User & Team Names are case sensitive

Crunching@EVGA is case sensitive

 
 
master_prpclient.ini
For X64 CPU Setups
 
For Chris21010

// email= is a REQUIRED field. The server will be use this address
// to send you an e-mail when your client discovers a prime.
email=Put the same email address you use on PG's Website.

// userid= is a REQUIRED field that will be used by the server
// to report on stats, etc. without having to reveal the user's
// e-mail address. DO NOT USE spaces. Instead use underscore _.
userid=bcavnaugh

// This value differentiates clients using the same e-mail ID
// DO NOT USE spaces. Instead use underscore _.
// I Use the same name as the Host name used on PG's Website.
machineid=BoincFolder

// This value differentiates instances on a machine
// This will be set automatically by the *-update-prpclient-ini script
// If you prefer to setup up prpclient directories manually, please
// set this to a unique identifier (e.g. 1,2,3,4...)
instanceid=INSTANCE_ID

// Tests completed by this "team" will be rolled-up as part of team stats. This
// will be recorded on tests that are pending and then updated when tests are
// completed. Since it is stored on the server per test, it is possible for a
// single user to be a member of multiple teams. If no value is specified for
// this field, then completed tests and primes will not be awarded to any teams.
// DO NOT USE spaces. Instead use underscore _.
teamid=Crunching@EVGA

// server= configures the mix of work to perform across one or more
// servers. It is parsed as follows:
// <suffix>:<pct>:<workunits>:<server IP>:<port>
//
// <suffix> - a unique suffix for the server. This is used to distinguish
// file names that are created for each configured server.
// <pct> - the percentage of PRP tests to do from the server.
// <workunits> - the number of PRP tests to get from the server. The 
// server also has a limit, so the server will never return
// more than its limit.
// <server IP> - the IP address or name for the server
// <port> - the port of the PRPNet server
//
// Setting pct to 0 means that the client will only get work from the
// server if it cannot connect to one of the other configured servers.
// Please read the prpnet_servers.txt in this directory for information
// on the latest PRPNet servers.

// The following servers are from PrimeGrid. To make a server active,
// you must remove the "//". For more information about proper settings
// please see the readme_primegrid.txt in this directory.
// For descriptions of each project, please see this thread:
// http://www.primegrid.com/forum_thread.php?id=1215&nowrap=true#13329
//server=121:0:1:prpnet.primegrid.com:12001
server=FPS:0:1:prpnet.primegrid.com:12002
//server=GCW:0:1:prpnet.primegrid.com:12004
//server=27:0:1:prpnet.primegrid.com:12006
//server=PRS:0:1:prpnet.primegrid.com:12008
//server=WIEFERICH:0:1:prpnet.primegrid.com:13000
//server=WALLSUNSUN:0:1:prpnet.primegrid.com:13001

// This is the name of LLR executable. On Windows, this needs to be
// the LLR console application, not the GUI application. The GUI 
// application does not terminate when the PRP test is done.
// On some systems you will need to put a "./" in front of the executable
// name so that it looks in the current directory for it rather than 
// in the system path.
// LLR can be downloaded from http://jpenne.free.fr/index2.html
// If running a 64-bit system, comment out the llr.exe and uncomment llr64.exe
//llrexe=llr.exe
llrexe=llr64.exe

// This is the name of the PFGW executable. On Windows, this needs to
// be the PFGW console application, not the GUI application.
// PFGW can be downloaded from http://tech.groups.yahoo.com/group/openpfgw/
// If you are running a 64 bit OS, comment out the pfgw32 line
// and uncomment the pfgw64 line.
//pfgwexe=pfgw32.exe
pfgwexe=pfgw64.exe

// This is the name of the executable used for Wieferich and Wall-Sun-Sun searches.
// Available ONLY to 64bit OS. Uncomment if you have 64bit OS.
// If you have an OpenCL-capable GPU, uncomment 'wwwwcl'
// I have No GPU in my T630 anymore so not used
//wwwwexe=wwww.exe
//wwwwexe=wwwwcl.exe
//wwwwexe=wwwwcl64.exe

// This sets the CPU affinity for LLR on multi-CPU machines. It defaults to
// -1, which means that LLR can run on an CPU.
// Would or wonder if this was set to say 6 it would run 1 Task with 6 Cores?
cpuaffinity=

// This sets the GPU affinity for CUDA apps on multi-GPU machines. It defaults to
// -1, which means that the CUDA app can run on an GPU.
gpuaffinity=

// Set to 1 to tell PFGW to run in NORMAL priority. It defaults to 0, which means
// that PFGW will run in IDLE priority, the same priority used by LLR, phrot,
// and genefer.
normalpriority=0

// This option is used to default the startup option if the PREVIOUS
// SHUTDOWN LEFT UNCOMPLETED WORKUNITS. If no previous work was left
// this will act like option 9.
// 0 - prompt
// 1 - Return completed work units, abandon the rest, then get more work
// 2 - Return completed work units, abandon the rest, then shut down
// 3 - Return completed, then continue
// 4 - Complete in-progress work units, abandon the rest, then get more work
// 5 - Complete in-progress work units, abandon the rest, then shut down
// 6 - Complete all work units, report them, then shut down
// 7 - Complete all work units then shut down (do not report completed work)
// 9 - Continue from where client left off when it was shut down
startoption=9

// stopoption= tells the client what to do when it is stopped with CTRL-C and there is
// work that has not been completed and returned to the server. Options 2, 5, and 6 will
// return all workunits. This will override stopasapoption. The accepted values are:
// 0 - prompt
// 2 - Return completed work units, abandon the rest, then shut down
// 3 - Return completed work units (keep the rest), then shut down
// 5 - Complete in-progress work units, abandon the rest, report them, then shut down
// 6 - Complete all work units, report them, then shut down 
// 7 - Complete all work units then shut down (do not report completed work)
// 9 - Do nothing and shut down (presumes you will restart with startoption=9)
// I use 5 only on the Firt Set of task to run using Ctrl-C and then once tasks have completed
// I use the same 5 but wait till the end of the Event to use Ctrl-C
stopoption=5

// stopasapoption= tells the client that it needs to be shutdown automatically, i.e. without
// a CTRL-C. It is evaluated after each test is completed. It should be 0 upon startup.
// The accepted values are:
// 0 - Continue processing work units
// 2 - Return completed work units and abandon the rest
// 3 - Return completed work units (keep the rest)
// 6 - Complete all work units and return them
// 7 - Complete all work units then shut down (do not report completed work)
stopasapoption=0

// Timeout on communications errors
// (default is 60 minutes, minimum is 1 minute if not specified here...)
// Note that the actual used in the client is anywhere from 90% to 110% of this value
errortimeout=1

// Size limit in megabytes for the prpclient.log file...
// 0 means no limit.
// -1 means no log.
loglimit=1

// Set the debug level for the client
// 0 - no debug messages
// 1 - all debug messages
// 2 - output debug messages from socket communication 
debuglevel=0

// Whether or not to echo "INFO" messages from server to console for accepted tests
// 0 - no echo
// 1 - echo (default)
echotest=1

 

Really hard for me to read the Forums ATM but I am setting some up now to run, and will report back.
Some info here: http://www.primegrid.com/forum_thread.php?id=7610
 
I have 6 running on my AMD and 12 on my T630 ATM.
Stats will be available at the well known place here.
My Pending http://prpnet.primegrid.com:12002/pending_tests.html
 

I am am, looks like I did it right.
I hope.

I added some more cores.
 
Just for the heck of it, since I have been playing with fast NVME and PCIe SSD drives on my x79 system
I sprung the 10 bucks and bought AMDs ramdisk drive software. I can make a drive up to 12gb.
Reason I paid for it is it makes a back up of the drive when it shuts down and mounts the drive with all its files on start up.
Wow, I thought NVME was so much faster than the SATAIII drives, the ramdisk drive puts them to shame.
Figure I will run BOINC and maybe folding off the ramdisk, and see how well it goes.
I made a 6gb disk and I have 16gb Gskill Sniper 1866

On dualxeon2670 the ID are all 3? did you change the instanceid=INSTANCE_ID
Should keep it at instanceid=INSTANCE_ID
Each Core will number you run will change in each prpclient.ini file based what you have in the master_prpclient.ini file.
That is what the Update Bat File does.
 
Setup your master_prpclient.ini from what is in Post#1
Run the 4-hex-install-prpclient.bat file then the 4-hex-update-prpclient-ini.bat file and last 4-quad-start-prpclient.bat file
If you want to stop after the Task has completed then in each DOS windows hit CTRL-C and then let them run until completed.
If you want to say run 5 Tasks then change (1,1,4) to (1,1,5) in the three files below and name them with a 5 in place of the 4.
From the 4-hex-install-prpclient.bat file using 4 Cores  
ECHO
for /l %%x in (1,1,4) do (
  mkdir prpclient-%%x
  cd prpclient-%%x
  copy /Y ..\programs\*.exe
  copy /Y ..\programs\*.dll
  cd ..
)
EXIT
//////////////////////////////////////////////////////////////////////////////////////////// 
From the 4-hex-update-prpclient-ini.bat file using 4 Cores  
ECHO
for /l %%x in (1,1,4) do (
  BatchSubstitute.bat INSTANCE_ID %%x master_prpclient.ini > prpclient.ini
  move /Y prpclient.ini prpclient-%%x\prpclient.ini
)
EXIT
//////////////////////////////////////////////////////////////////////////////////////////// 
4-hex-start-prpclient.bat file using 4 Cores  
ECHO
for /l %%x in (1,1,4) do (
  cd prpclient-%%x
  start "prpclient-%%x" /MIN prpclient.exe
  cd ..
)
EXIT
 
 

 
As the 4-hex-update-prpclient-ini.bat file runs updating each ini file.

FYI our Team Name is Case Sensitive, sorry.

Crunching@EVGA is case sensitive

 

I read that you could change the prpclient file on the run when it is still running.
So I changed the small c to a cap C in the teams name, hit update prpclient
Noticed today one more task went to the small c crunching..... team dang it.
Sorry about that, at least I get the credit, would rather the team did too.
I shut down the system then ran the update prpclient batch file and it moved the file like I believe it should have.
Sure hope it works
 
On another note, the system running on the ram drive is on its 4th task while the other sys close to it in spec is on its 2nd/4rd tasks.
 
It is a 4930k vs an e5-1650 (3930k) roughly the same speed Ivy vs Sandybridge. But the memory is 1866 where the sandy has ram at 2133
Never really seem much difference before on projects
 
So. what I will do is get another x79 mb out and install an e5-1650 so I have 3 alike running.
One will have a Sata3, one a NVME pcie drive and another one on a ram disk.
Even if I use the free 4gb ram drive, no need to save a test drive for testing
Set the ram speed and timings all the same, see what is faster.
 

One update on the ramdrive, I shut down and rebooted this system to update the client file.
The ramdrive did save and it reloaded fine, the tasks started right back up after I ran the update client batch.
I am pleased with it so far, nice to have the modern fast NVME drive in this x79 system and an even faster ramdrive.
Cant wait to get it running in my x58 system too. Who says you have to upgrade the MB to get modern drives to work....
It is the Classified3 with a bunch of PCIE slots, going to put a couple two or three 980Ti in there.
Be the heater upstairs this Winter. Nice board, hate to sell it, so might as well get the most out of it.

challenge is over. 1,314 tests were done.

Congratulation to
- the top users
rank UID tests score
1 Grebuloner 309 4,515,402
2 bcavnaugh 202 2,972,061
3 bill1024 109 1,604,020
4 Lumiukko 88 1,292,715
5 Williamd007 84 1,234,925


- the top teams
rank team ID tests score
1 The_Knights_Who_Say_Ni! 411 6,015,437
2 Crunching@EVGA 304 4,473,381
3 Aggie_The_Pew 127 1,867,752
4 PrimeSearchTeam 88 1,292,714
5 AMD_Users 24 353,315

permalink to the stats: http://u-g-f.de/PRPNet/2017_09_FPS_Challenge.html

bill1024

I found out that the team name is case sensitive when editing the prpclient.
So make sure to type it in exactly as it should be.
So will crunching@EVGA er Crunching@EVGA take two of the top ten spots....oops
Sorry about that.

Yes, user and team are case sensitive, should this be explained in the prpclient.ini-comments?
____________