PRPNet's Fool's Day mini Challenge

1 April is April Fool's Day. 1 is not a prime number...however, 2 is. ;) Therefore, on 2 April 2010 18:00 UTC a mini Challenge is being offered in PrimeGrid's PRPNet. With this mini Challenge, we hope to accomplish two goals: 1) stress test PRPNet for an extended period of time; and 2) help the PPSE project reach n=500K sooner.

There is an initial primary stress test which will last for 24 hours ending 3 April 2010 18:00 UTC. If all goes well, there will be an extended stress test that will last until 9 April 2010 18:00 UTC.

PRPNet v3.2.3alpha has proven to be very stable. A BIG thank you to Mark Rodenkirch for getting PRPNet to this point. Numerous internal stress tests have been successfully completed. However, there's nothing like a good old public stress test to shake out those "hard to find" bugs. If you are available and have the resources to participate, please consider at least the first 24 hours. If you are able to stay longer, that's even better.

To participate, download the new v3.2.3alpha client and insert this line in your master_prpclient.ini file and update:

server=PFDMC:100:5:pgllr.mine.nu:7171

Make sure to comment out or zero out port percentages for the rest of the ports. Feel free to set a range of cache from 1 to 20. WU deadline is set at 6 hours.

Application builds are available for the following:

3.2.3alpha archives

• prpclient-3.2.3alpha-linux (32 bit - will run on 64 bit)
  
• prpclient-3.2.3alpha-windows (32 bit - will run on 64 bit)
  
• prpclient-3.2.3alpha-macintel
  
• prpclient-3.2.3alpha-macppc
  
• prpclient-3.2.3alpha-ps3
  
• prpclient-3.2.3alpha-ultrasparc32
  
• prpclient-3.2.3alpha-ultrasparc64
  

For more information about PRPNet and to download the new builds, please see the PRPNet thread.

Stats can be viewed here:

Server Stats
Pending Tests
User Stats
User Primes
____________

Am I to assume that this server is not loaded (or loaded correctly) at this time?

Am I to assume that this server is not loaded (or loaded correctly) at this time?

server=PFDMC:100:5:pgllr.mine.nu:7171

Download of http://pgllr.mine.nu/PRPNet/prpclient-3.2.3alpha-linux.zip fails at the moment

503 Service Unavailable

[EDIT: ignore - working now]

BTW http://pgllr.mine.nu:7171/server_stats.html shows min N and max N in the column headings instead of min K and max K
____________

server=PFDMC:100:5:pgllr.mine.nu:7171

will this server last longer ???
If your answer is 'yes' I will include it into stats this evening ...

Less than 20 Minutes till start!!!

The Mini Challenge is about to begin. This is an informal gathering of resources to stress test the PRPNet software. We'll do our best to keep track of "unofficial" scores for the 24 hours of the initial stress test. We'll also extend that to 9 April to get a rough estimate of rankings.

As with all work completed in the PSA, this too will receive manual cobblestones.

As a precaution against idle cores in case something happens, it is recommended to list another port available. An example is listed below:

server=SGS:0:1:prpnet.primegrid.com:12000

By having a resource share of 0, this tells PRPNet only to download work if the other port is unreachable. Having a cache of 1 allows PRPNet to go back to request work from the other port rather quickly.
____________

PRPNet's Fool's Day mini Challenge - UPDATE

1 hour into the stress test and PRPNet is not even breaking a sweat! :) It's taking a nice stroll in the park and stopping to smell the flowers. We need to put a little fire under its feet to bring it at least up to a jog. :D

Actually, this just means that PRPNet is holding up strong. However, if you have more resources you can add, please consider adding them to the mini challenge...or spread the word for more users to come.

Thank you.
____________

The servertype is wrong (thus affecting server_stats.html). It should be a Fixed K server, not a Fixed N server.

PRPNet's Fool's Day mini Challenge - UPDATE

3 hours into the stress test and PRPNet STILL is not breaking a sweat! :) This is GREAT news so far. We hope that as the mini Challenge continues, more people will see the success and decide to add their cores to the stress test.

This is proving to be a big boost for the PRPNet software.

Thank you to everyone participating and answering the call for more "stress". Rest assured that in cases like this, it's the only time we like "stress". ;)

Please spread the word for more users to come.
____________

PRPNet's Fool's Day mini Challenge - UPDATE

Scotty: [the USS Enterprise is being sucked into a black hole] I'm giving her all she's got, Captain!
James T. Kirk: All she's got isn't good enough!

These primes make the Top 5000 list. If you wish to submit the primes yourself, please use your PPSE proof code. If you do not have one, create a new code with the standard PPSE credits:

Primality program: LLR
Additional credits: PG, PSieve, Srsieve

Be sure to add the Descriptive data section.

If you have auto reporting selected in your PG BOINC preferences, then the prime will be submitted on your behalf.
____________

PRPNet's Fool's Day mini Challenge - UPDATE

Not much to report. It's still a walk in the park for PRPNet. It's holding up very well to the "stress" testing. :)

33 Users, 46K+ tests, 7 primes
Stats can be viewed here:

Server Stats
Pending Tests
User Stats
User Primes
____________

PRPNet's Fool's Day mini Challenge - UPDATE

The initial 24 hour stress test has completed and PRPNet did more than just survive, it THRIVED!!! Actually, I think I hear it laughing at us saying, "Is that all you got?" :D

Thank you to everyone who participated. It was a very nice success. This port will remain active for another 6 days as we will continue to stress it. If you have the resources, please consider leaving them here so that we can let the database grow and get a good indication if that will create any problems.

37 Users, 50K+ tests, 8 primes

Stats can be viewed here:

Server Stats
Pending Tests
User Stats
User Primes
____________

Why are some primes hidden on

http://pgllr.mine.nu:7171/user_primes.html

It seems to be time to load more into the server. There aren't many untested candidates left

It seems to be time to load more into the server. There aren't many untested candidates left

It seems to be time to load more into the server. There aren't many untested candidates left

Now I loaded work with full load, and there was no problem..

1. When prpclient finds a +1 prime, it uses pfgw to check for xGFN divisibility. Right now when pfgw runs, it does a prp test before it tests for xGFN divisibility. This is not necessary as the prime has already been proven by LLR. Therefore, in the next release, pfgw will skip the prp test and go straight to xGFN divisibility testing.
   
2. pfgw is prevented from running by security software. If pfgw is not allowed, then xGFN divisibility testing is not done. Users will need to resolve this by modifying their security settings to allow pfgw to run.
   
3. For +1 primes, the e-mail sent out says that the number has not been tested for xGFN divisibility when, in fact, it has.
   

#1 and #3 should be fixed in the next release.
____________

A few things have popped up during past couple of days but they are very minor:

1. When prpclient finds a +1 prime, it uses pfgw to check for xGFN divisibility. Right now when pfgw runs, it does a prp test before it tests for xGFN divisibility. This is not necessary as the prime has already been proven by LLR. Therefore, in the next release, pfgw will skip the prp test and go straight to xGFN divisibility testing.
   
2. pfgw is prevented from running by security software. If pfgw is not allowed, then xGFN divisibility testing is not done. Users will need to resolve this by modifying their security settings to allow pfgw to run.
   
3. For +1 primes, the e-mail sent out says that the number has not been tested for xGFN divisibility when, in fact, it has.
   

#1 and #3 should be fixed in the next release.

I have posted all binaries for PFGW 3.3.4 here: http://sourceforge.net/projects/openpfgw/files/.

There is only one change to this release. GFN testing will output a string "GFN testing complete" after it has completed. This message will be used as an affirmation to the PRPNet client (3.2.4, when that is released) that GFN testing completed and was not cancelled.

The 3.2.4 PRPNet client will not report that GFN testing is complete unless using this release. Right now the 3.2.3 PRPNet client has no way to verify that it completed. You can use PFGW 3.3.4 with the 3.2.3 client. It will not affect what the client reports to the server.

We are really walking on the edge in the PFDMC. ;-)
Just got another prime submission with an entrance rang of 4999,
that is already the second one which is really close for the top 5000 :-DDD
____________

A little off-topic question: the client says <insert number here> is prime. Then it ran a test and now it says <insert number here> is 3-PRP. Then it started another test, running GF_sprime_5.
My question follows: what's a 3-PRP? I assume the latest test checks if it's a Gen. Fermat divisor.

We are really walking on the edge in the PFDMC. ;-)
Just got another prime submission with an entrance rang of 4999,
that is already the second one which is really close for the top 5000 :-DDD

When are we likely to hit 500k. I had two primes place at 5001 today.
2493*2^496646+1
8177*2^496667+1

Top 5000 List - update

Sadly, it's official. We are just crunching for pride up to n=497K. To make the Top 5000 list, primes must be greater than 497K.

A consolation is that 497K-498K will be skipped since it was already completed. Currently a prime at 498K enters the list at position 4942. A prime at 499K enters at position 4912. Unfortunately, as primes are found above this, these numbers will increase.

The challenge will be to complete the 498K-499K range before 58 primes are found above that range. To monitor the bottom of the envelope, please see: 4900th-5000th primes
____________

We appear to have ran out of work. Will the 498K range be started up on this server? Do I need to switch or should I wait for the jobs to be loaded on the 7171 Server?

The user_stats on 7171 are now completely different ?

Is there something mixed up ? Or is that just an alias for another "server" ?


EDIT: Ah seems better now, thx.
____________

Port 7171 seams to be Down? How long?

Is there any indication when it will be back up? Thanks.
____________
May the Force be with you always.

OK, it is back up now.
____________
May the Force be with you always.

Is there any indication when it will be back up? Thanks.

ATTENTION!!!

PPSE BOINC has received an additional boost and is now encroaching on 7171's leading edge. Therefore, PPSE will be cut short at n=498850. Please add additional ports to your prpclient.ini file to keep your cores active. For example, if you currently have:

server=PFDMC:100:1:pgllr.mine.nu:7171

you could add a 0% share that PRPNet will switch to once port 7171 is empty. For example:

server=GCW13:0:1:prpnet.primegrid.com:12004

Although listed at 0%, when 7171 is empty, 1 WU at a time will be requested from port 12004. You could also split shares between other ports (make sure they add up to 100%) or switch back to BOINC. Once 7171 is empty, please comment out that port.

Port 7171 has served its purpose. First as a testing ground for PRPNet and later as a savior to the PPSE primes to keep them from falling off the Top 5000. BOINC PPSE has now caught up and established a small buffer between the leading edge of the search and the bottom of the Top 5000 list.

Please consider heading over to GCW13 port 12004 for a few days for a belated GCW13 mini Challenge.

server=GCW13:100:1:prpnet.primegrid.com:12004

Thank you to everyone for helping with the port 7171 effort. It was a splendid success.
____________

Is the prpclient.ini fie dynamic .... just make the changes and active prpclient will pick up the change

Or is it static, Do I need to stop the prpclient and restart to pick up the change to the prpclient.ini file?

1. Update master_prpclient.txt
   
2. Run "4-quad-update-prpclient-ini" to update all the folders
   
3. Stop each instance of prpclient
   
4. Run "4-quad-start-prpclient" to restart all instances
   

____________

ATTENTION!!!

PPSE BOINC has received an additional boost and is now encroaching on 7171's leading edge. Therefore, PPSE will be cut short at n=498850.

ATTENTION!!!

PPSE BOINC has received an additional boost and is now encroaching on 7171's leading edge. Therefore, PPSE will be cut short at n=498850.

seems to me we reached it:

[2010-04-15 19:05:47 GMT] PFDMC: INFO: No available candidates are left on this server.

last test from me was:

[2010-04-15 19:05:24 GMT] PFDMC: INFO: Test for 7937*2^498851+1 was accepted

so we go one with other ports ?!!!

for stats-freaks: I will move port 7171 to ancient stats if there isn´t any progress / any pending ....

So what exactly happened to PPSE? It seem that both PPSE ports (10,000 an 11,000) for n < 500K and n > 500K are both loaded with n < 500K.

So what exactly happened to PPSE? It seem that both PPSE ports (10,000 an 11,000) for n < 500K and n > 500K are both loaded with n < 500K.

So what exactly happened to PPSE? It seem that both PPSE ports (10,000 an 11,000) for n < 500K and n > 500K are both loaded with n < 500K.

I know this is a bit old, but I'm wondering about this as well. I couldn't find any answers in other threads.

Ok, then you way want to change this post that says port 12007 is retired: http://www.primegrid.com/forum_thread.php?id=1215&nowrap=true#13329

Thanks for the information.
____________