PRPNet released!

[henryzz]

Originally Posted by rogue

Right now you can't. I'll do it for the next release.

BTW, are you saying that you want PFGW to run in normal priority? Can I ask why? If this is a main computer or one with a single CPU, that could significantly hurt the performance of the PC.

It is a main pc. I have got used to it being slightly sluggish(my old pc was with nothing running).
I am using prpnet with pfgw to absorb wasted cycles from a four core gnfs which for some reason only uses up ~3 cores between 4 sievers on linux.
I want to be able to run a couple of llrs in the background so that when factmsieve.pl is postprocessing or prpnet is communicating 100 results(really quick to process) it doesn't waste cpu cycles.

[rogue]

Originally Posted by Cruelty

I've found out what was causing it:

frequency=60

When the client was connecting each 60 minutes not all results were ready yet at that point of time.
BTW: what is the reason for this variable anyway?

This variable forces the client to report results back to the server after a specified amount of time regardless of how much work was done. This is a holdover from ECMNet. I could probably remove it. Would anyone have objections to that?

Originally Posted by henryzz

I am using prpnet with pfgw to absorb wasted cycles from a four core gnfs which for some reason only uses up ~3 cores between 4 sievers on linux.
I want to be able to run a couple of llrs in the background so that when factmsieve.pl is postprocessing or prpnet is communicating 100 results(really quick to process) it doesn't waste cpu cycles.

Adding support for that should be easy, but there are caveats. Most of the other software you are running will run at IDLE priority. PFGW will steal cycles from the other processes. As you have four cores, that shouldn't be too big a deal. I would not recommend the setting for a single core PC.

[Lennart]

Originally Posted by rogue

This variable forces the client to report results back to the server after a specified amount of time regardless of how much work was done. This is a holdover from ECMNet. I could probably remove it. Would anyone have objections to that?

For me you can remove it.

Lennart

[mdettweiler]

Originally Posted by Lennart

For me you can remove it.

Lennart

Ditto here.

[Cruelty]

Originally Posted by rogue

This variable forces the client to report results back to the server after a specified amount of time regardless of how much work was done. This is a holdover from ECMNet. I could probably remove it. Would anyone have objections to that?

It might make sense in certain configurations, but it should behave a little bit different. IMO server should be notified that the client is still working on specified work and as a result extend the "reservation" period. This might become important in the future when PRPnet will be used to test much larger exponents.
BTW: I have set up prpclient on a remote computer running as a service. Is it possible that at shutdown / restart of the PC prpclient will force cllr.exe to save current status, so that after restart it will start exactly where it left?

[rogue]

Originally Posted by Cruelty

It might make sense in certain configurations, but it should behave a little bit different. IMO server should be notified that the client is still working on specified work and as a result extend the "reservation" period. This might become important in the future when PRPnet will be used to test much larger exponents.
BTW: I have set up prpclient on a remote computer running as a service. Is it possible that at shutdown / restart of the PC prpclient will force cllr.exe to save current status, so that after restart it will start exactly where it left?

I could possibly use that as a "heartbeat" to tell the server that the client is still actively working, but if that were the case I would probably hide it from the user and put it into a separate thread. Otherwise it would require to client to stop and restart.

Regarding the shutdown/restart, that is really a question for cllr. If it creates an appropriate temp file then it will start the test where it stopped when it restarted.

[Cruelty]

Originally Posted by rogue

Regarding the shutdown/restart, that is really a question for cllr. If it creates an appropriate temp file then it will start the test where it stopped when it restarted.

while running in normal window and pressing ctrl+c temp file is created and then application restarts from that point, however closing system when running either in window mode or as a service does not produce the temp file... not sure if this is an issue with cllr or prpclient

[mdettweiler]

Originally Posted by Cruelty

while running in normal window and pressing ctrl+c temp file is created and then application restarts from that point, however closing system when running either in window mode or as a service does not produce the temp file... not sure if this is an issue with cllr or prpclient

Actually, I think that's not an issue with either, but rather with Windows. When shutting down, Windows' behavior regarding this can be rather hard to predict. For example, I've seen Windows halt its shutdown indefinitely to wait for a user to give a response to PRPnet's shutdown prompt when stopoption is set to 0. Yet, I'm not sure if it actually can tell cllr.exe to shut down properly. Windows process signals are rather limited compared to what's available in Linux, and thus it's somewhat harder to tell an application to shut down "properly".

Observation is probably the best way to figure out how it will behave in this regard. To that end, I've noticed on one of my machines which runs PRPnet as a service that it *doesn't* seem to produce save files when I shut down the client through services.msc or "net stop". Your mileage may vary, however.

[PCZ]

rogue

Is there a way to make prpnet remove completed tests from the candidates file. ?
Seems that all the tests i have done are still in the candidates file and it is growing very large.

Server is now using more and more processing time updating the candidates file as its size is increasing..

[PCZ]

Trying a newer version and it is removing inactive tests.

[rogue]

Originally Posted by PCZ

rogue

Is there a way to make prpnet remove completed tests from the candidates file. ?
Seems that all the tests i have done are still in the candidates file and it is growing very large.

Server is now using more and more processing time updating the candidates file as its size is increasing..

It will remove if you have double-checking turned off. If you have double-checking turned on, it will wait for a second test with a matching residue. Read the prpserver.ini file.