Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Number crunching :
Turn off report results immediately to help server load?
| Author |
Message |
|---|
|
|
|
Now we're all first because of the new fast-checking algorithms, is there any need for reporting results immediately? It might ease the server load (if there is one). Of course anyone who objects would be free to set this parameter locally. | |
|
 Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13955
ID: 53948
Credit: 392,606,292
RAC: 174,937
                               
|
Now we're all first because of the new fast-checking algorithms, is there any need for reporting results immediately? It might ease the server load (if there is one). Of course anyone who objects would be free to set this parameter locally.
It won't affect the server load either way, so set it however you want. More specifically, while it will indeed lower the server load by some measurable amount, this isn't what causes problems. It is the validation on the main tasks that is resource intensive, not servicing the RPCs from your computers. It won't make a difference whether you have it on or off.
Personally, I'm leaving it on because I do run SGS from time to time, and both SGS and GFN-15 still don't have FAST-DC so being first is still a race. If I turn it off, I won't remember to turn it back on when I need it.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
But I have
<report_results_immediately>0</report_results_immediately>
under each app and the whole project in app_config, and it's ignored. The server seems to be overriding my request. | |
|
|
|
|
This should be in the cc_config ... | |
|
|
|
This should be in the cc_config ... As usual with Boinc, it's messy. You can have it in both. CC-config seems to apply to all projects, app_config applies to only one. Not sure which takes precedence. Anyway I have both set to 0, so the server seems able to override both my requests. Michael suggested I had a choice. Last time I asked years ago I was told I didn't have a choice.... | |
|
|
|
|
If i look at the boinc wiki, in the app_config is only "<report_results_immediately/>" specified.
So disabling this is only possible in the cc_config .. as i interpret this.
It might be possible that putting "<report_results_immediately>0</report_results_immediately>" in the app_config is interpreted as setting it to "True" as well.
| |
|
|
|
If i look at the boinc wiki, in the app_config is only "<report_results_immediately/>" specified.
So disabling this is only possible in the cc_config .. as i interpret this.
It might be possible that putting "<report_results_immediately>0</report_results_immediately>" in the app_config is interpreted as setting it to "True" as well.
I'm lost. The same instruction is in both app and cc for me. Should it be worded differently?
Your first mention of it above "<report_results_immediately/>" doesn't parse in my head. There should be two entries with a number inbetween, either 0 or 1.
To be clear,
In cc_config I have: <report_results_immediately>0</report_results_immediately> near the end of the options section.
In app_config I have: <report_results_immediately>0</report_results_immediately> right at the end, and also within each app section.
I've never seen <report_results_immediately/> with the slash at the end. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13955
ID: 53948
Credit: 392,606,292
RAC: 174,937
|
Your first mention of it above "<report_results_immediately/>" doesn't parse in my head. There should be two entries with a number inbetween, either 0 or 1.
Syntactically, <report_results_immediately/> is identical to <report_results_immediately>1</report_results_immediately>. It's an XML shorthand. Any code that is parsing XML correctly will accept either. Note the different location of the slash.
____________
My lucky number is 75898524288+1 | |
|
|
|
Your first mention of it above "<report_results_immediately/>" doesn't parse in my head. There should be two entries with a number inbetween, either 0 or 1.
Syntactically, <report_results_immediately/> is identical to <report_results_immediately>1</report_results_immediately>. It's an XML shorthand. Any code that is parsing XML correctly will accept either. Note the different location of the slash.
Ok thanks. So my question remains, how do I stop it reporting immediately? I have a zero in both configs. You suggested earlier it was up to me, but the server seems to be overriding my choice. | |
|
|
|
|
There is only a 7 second delay asked for from the PrimeGrid server. 7 seconds is not very long and close to immediate really.
After 7 seconds your computers are free to report work and ask for more.
Climate Prediction, as you know, makes you wait an Hour (over 3600 seconds) before you can report anything, determined by the server, whether you have report results immediately or not.
So sometimes your settings are not going to change what the project is set up to do.
Perhaps this is what you are encountering?
Conan
____________
 | |
|
|
|
There is only a 7 second delay asked for from the PrimeGrid server. 7 seconds is not very long and close to immediate really.
After 7 seconds your computers are free to report work and ask for more.
Climate Prediction, as you know, makes you wait an Hour (over 3600 seconds) before you can report anything, determined by the server, whether you have report results immediately or not.
So sometimes your settings are not going to change what the project is set up to do.
Perhaps this is what you are encountering?
Conan
Actually, that delay doesn't prevent reporting tasks, it only prevents getting new tasks. I think Boinc sticks to it anyway, but I've done a manual update to send work back before shutting off a machine for maintainance, and the server took it. I was just refused new work.
Primegrid is doing something different, it's telling my Boinc to report anything completed right now, instead of waiting until the next time it happens to ask for work etc. | |
|
|
|
|
Whoever is spamming this thread and causing email notifications, don't bother. I can't see your posts. | |
|
|
|
|
I remember Michael Goetz writing that report_results_immediately was set in the server.
A serch in the forum hit this 2018 message https://www.primegrid.com/forum_thread.php?id=7814&nowrap=true#114331.
It's was posted in the Aggie The Pew forum area.
Hope that anyone can read and that it helps clear out the matter somehow (and not complicate it even more :) )
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
|
|
|
You mean this?
******
<report_results_immediately> is set by our server on every task. It makes no difference whether you include it or not.
The reason you were the double checker is because there was almost a two minute delay between when your computer finished the task and uploaded the result file and the time when your computer reported to the server that the task was complete.
Normally that shouldn't happen. It's exactly why I asked BOINC to make <report_results_immediately> settable from the server.
******
Back to my original post, this could be removed now we aren't racing to be first for most of the tasks. Of course you're free to set it locally anyway. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13955
ID: 53948
Credit: 392,606,292
RAC: 174,937
|
Now we're all first because of the new fast-checking algorithms, is there any need for reporting results immediately? It might ease the server load (if there is one). Of course anyone who objects would be free to set this parameter locally.
There's actually a new wrinkle on this subject. From the project's perspective, we absolutely, positively, without any doubt want the results returned as quickly as possible.
As you may know, when you find a prime, the server often (all GFNs and most LLR tasks) has to do lengthy follow up tests. As we found out recently, bad(TM) things happen if we run those tests before you report the task as complete. If the result file is sent to us but your computer hasn't reported the task is complete, we have to delay the testing.
We kindly request, therefore, that you let your computers return the results immediately.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Why the hurry? Why can't the server just wait? | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13955
ID: 53948
Credit: 392,606,292
RAC: 174,937
|
Why the hurry? Why can't the server just wait?
The tests can be very long. If the server is available, we prefer to have it doing something useful. Later on, there might be a lot of tests that need to be done. We prefer the flexibility to start the tests when we want to do so.
____________
My lucky number is 75898524288+1 | |
|
Post to thread
Message boards :
Number crunching :
Turn off report results immediately to help server load? |
