| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home
Thread: Release of new FightAIDS@Home application versions on BOINC |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 43
|
|
| Author |
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
knreed posted the below in member news. If there are any questions on these precedings, please append them to this post and we'll endeavour to collect and answer them.
---------------------------------------- Release of new FightAIDS@Home application versions on BOINC We are approaching the point where we will be releasing the new application version of FightAIDS@Home. This will occur mid to late next week. This transition will be a little bumpy due to the fact that the workunits we are currently running with the current version of the FightAIDS@Home application can cause the new version to experience errors and compute incorrect results. Additionally, the workunits that work with the new application version will not run correctly under the old application version. This means that we need to ensure that all of the workunits built to run under the old application version are completed and validated prior to the change. In order to make the transition as quick as possible we will be doing the following steps: 1) As of now, FightAIDS@Home workunits sent out will have a deadline of 4 days instead of the current 9 day deadline. 2) Starting on late Saturday and early Sunday, workunits sent out will have a deadline of 2 days. Sometime, most likely early on Wednesday, the final workunits for the current FightAIDS@Home application version will be sent out. At that time, there will be times where no work is available for FightAIDS@Home. In order to minimize this time, we will take steps to get those workunits validated quickly. All members are reminded that they can check the box 'If there is no work available for my computer for the projects I have selected above, please send me work from another project (this option only applies to BOINC agents).' on the My Projects page so that they can ensure that they receive work even if we are temporarily not sending work for FightAIDS@Home. Once the new application version is released, we will return to normal 9 day deadlines. There will be one additional positive change to processing - we will be reducing the redundancy to 2 instead of 3 for the workunits. This will allow us to complete nearly 50% more workunits with the same number of devices participating. ---------------------------------------- [Edit 1 times, last edit by knreed at Aug 2, 2007 4:57:18 PM] [Aug 2, 2007 4:57:05 PM]
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There will be one additional positive change to processing - we will be reducing the redundancy to 2 instead of 3 for the workunits. This will allow us to complete nearly 50% more workunits with the same number of devices participating. ---------------------------------------- [Edit 1 times, last edit by knreed at Aug 2, 2007 4:57:18 PM] [Aug 2, 2007 4:57:05 PM] Could someone please explain this quorum?  [Edit 1 times, last edit by Former Member at Aug 2, 2007 5:03:34 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Instead of 3 results required for a quorum, only 2 will be required.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Instead of 3 results required for a quorum, only 2 will be required. I understand the sentence...but I don't understand how it's applied. If the two match exactly they're OK; if not send out another? This is due to what differences in the application? |
||
|
|
Papa3
Senior Cruncher Joined: Apr 23, 2006 Post Count: 360 Status: Offline Project Badges: 
|
Instead of 3 results required for a quorum, only 2 will be required. I understand the sentence...but I don't understand how it's applied. If the two match exactly they're OK; if not send out another? This is due to what differences in the application? What you are describing is exactly what they plan to do  Before, they were requiring a match between all 3 results in order to confirm a result. That was being a bit too conservative, so they are now relaxing a little and going with a more reasonable 2-result approach to confirmation. An excellent idea, IMO. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Instead of 3 results required for a quorum, only 2 will be required. I understand the sentence...but I don't understand how it's applied. If the two match exactly they're OK; if not send out another? This is due to what differences in the application? What you are describing is exactly what they plan to do Before, they were requiring a match between all 3 results in order to confirm a result. That was being a bit too conservative, so they are now relaxing a little and going with a more reasonable 2-result approach to confirmation. An excellent idea, IMO. So this is a policy change by WCG to be implemented for future projects also? |
||
|
|
Papa3
Senior Cruncher Joined: Apr 23, 2006 Post Count: 360 Status: Offline Project Badges:
|
So this is a policy change by WCG to be implemented for future projects also? No, it's just a FAAH policy change. Each WCG project has its own quorum policy. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Instead of 3 results required for a quorum, only 2 will be required. I understand the sentence...but I don't understand how it's applied. If the two match exactly they're OK; if not send out another? This is due to what differences in the application? What you are describing is exactly what they plan to do Before, they were requiring a match between all 3 results in order to confirm a result. That was being a bit too conservative, so they are now relaxing a little and going with a more reasonable 2-result approach to confirmation. An excellent idea, IMO. So this is a policy change by WCG to be implemented for future projects also? Eso, i think knreed made announcement some time ago about potential for reducing quorum. Like presently quorum 3 and initial replication 3, it will for FA@H update be Quorum 2, Initial Replication 2. I suppose it's in the light of "trustworthy computing" As for the transition i wonder if the distribution system is able to know if a client still holds buffered tasks of e.g. FA@H version 5.28 and not send any new until all are returned? If there were a version identifier, is could ease the compatibility conflicts.... seen those upgrade dilemma's at other projects.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Aug 2, 2007 6:07:28 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
One of the things I did was suspending all HPF2 jobs to let the later due dated FA@H go first. Some of them have return requirements of week after Saturday the 11th. With BOINCview it was rather easy as it allowed a single action multi device selection and postponing of these tasks to let the 30 odd buffered FA@H go first.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
As for the transition i wonder if the distribution system is able to know if a client still holds buffered tasks of e.g. FA@H version 5.28 and not send any new until all are returned? If there were a version identifier, is could ease the compatibility conflicts.... seen those upgrade dilemma's at other projects. Unfortunately - no. There are several projects that would like the ability for workunits to be associated with a specific application version once they are assigned, but no mechanism currently exists. Thus we will have to make sure all current workunits are done processing before we release the new application version. |
||
|
|
|