Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
General discussion :
What happens to LLR2 if one person is using app_info?
| Author |
Message |
|---|
|
|
|
As I understand it, app_info pretty much allows a user to use any program they want to run a task as long as they return a valid result. This can mean, for example, using an older version of LLR instead of the latest version.
What happens to the workflow of LLR2 if someone is using app_info, aka anonymous platform, in an LLR2-enabled project? Normally one person does a full run of the task and then another person double-checks it using the quick method. I can think of 2 scenarios:
1) If the first person is using app_info to run regular LLR, then the special certificate files aren't uploaded, so I guess they can't be used for quick double-checking -- does the second person then have to do a full test or does something else happen instead?
2) If the first person uses LLR2 and generates the certificates, but the second person is running regular LLR using app_info ... will the task simply error for them, or will they just have to do a full test instead?
Hopefully the questions I've asked make sense - thanks in advance. :)
____________
8915 × 2 ^ 1507177 + 1 -- 453,710 digit PPSE
6603 × 2 ^ 1411654 + 1 -- 424,955 digit PPSE (DC) | |
|
|
|
|
BOINC server expects a certain number of files uploaded in a LLR2 task. If not all files are present when the tasks errors out and a new one is generated in the same workunit. For a certificate validation task, BOINC server expects a specific result. If it gets anything but it, the task errors out and a new one is generated in the same workunit. If validation repeatedly fails then admin action is required. Something's messed up. | |
|
 Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13513
ID: 53948
Credit: 236,922,854
RAC: 0
                           
|
As I understand it, app_info pretty much allows a user to use any program they want to run a task as long as they return a valid result. This can mean, for example, using an older version of LLR instead of the latest version.
What happens to the workflow of LLR2 if someone is using app_info, aka anonymous platform, in an LLR2-enabled project? Normally one person does a full run of the task and then another person double-checks it using the quick method. I can think of 2 scenarios:
1) If the first person is using app_info to run regular LLR, then the special certificate files aren't uploaded, so I guess they can't be used for quick double-checking -- does the second person then have to do a full test or does something else happen instead?
2) If the first person uses LLR2 and generates the certificates, but the second person is running regular LLR using app_info ... will the task simply error for them, or will they just have to do a full test instead?
Hopefully the questions I've asked make sense - thanks in advance. :)
This is, indeed, one of those changes that will break tasks on computers running app_info. We try to avoid this when possible, but this is not one of those times.
LLR2 fast double checking is not backwards compatible with the old LLR.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
I guess a user can (in theory) redirect the task to any software they want, using app_info, as long as that software produces precisely the same output (same number of files and same contents in the files) as does LLR2, the "official" program in the relevant subproject.
As said above, should the alternative software produce something else, that should be marked as either "error" or "invalid" (and not affect other users). Clearly, standard old LLR is not capable of producing the Pietrzak checkpoints or whatever LLR2 uses.
/JeppeSN | |
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 834
ID: 301928
Credit: 488,466,944
RAC: 0
               
|
|
I strongly suggest against using app_info with LLR2. LLR2 is still a work in progress, it's developing rapidly and different versions or file formats may be incompatible. We can sort this out on the server side, but only when server is sure which LLR version has been used on client. Sticking to specific version with app_info may cause incompatible results, not accepted by server, wasting CPU time.
Note that if app_info was used only to disable badly performing AVX-512, now it must be done in different way, using app_config statement:
<cmdline>-c -oCPUSupportsAVX512F=0</cmdline>
(I've omitted other app_config entries describing application and plan class).
| |
|
Post to thread
Message boards :
General discussion :
What happens to LLR2 if one person is using app_info? |
