Results 1 to 10 of 21

Thread: Help Conquer Cancer app_info.xml files

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Gold Member
    Slicker's Avatar
    Join Date
    October 25th, 2010
    Location
    South of Cheeseland
    Posts
    1,253

    Re: Help Conquer Cancer app_info.xml files

    WCG doesn't want people using an app_info.xml file. In fact, due to a bug in recent versions, BOINC ignores that the platform is not allowed and a fix is in place which will keep future versions from working with it if the project doesn't allow it. The app_config.xml is allowed though, regardless of the platforms allowed by the server, so that's the best option.

    Then again, you may be able to include the platform element in the app_info.xml file to get it to work anyway. If that works, don't tell DA!
    Spring 2008 Race: (1st Place)

  2. #2
    Silver Member
    nanoprobe's Avatar
    Join Date
    August 27th, 2012
    Location
    Classified
    Posts
    810

    Re: Help Conquer Cancer app_info.xml files

    Quote Originally Posted by Slicker View Post
    WCG doesn't want people using an app_info.xml file. In fact, due to a bug in recent versions, BOINC ignores that the platform is not allowed and a fix is in place which will keep future versions from working with it if the project doesn't allow it. The app_config.xml is allowed though, regardless of the platforms allowed by the server, so that's the best option.

    Then again, you may be able to include the platform element in the app_info.xml file to get it to work anyway. If that works, don't tell DA!
    There was also a bug found in the WCG server code that was allowing the app_info platform to work. The techs have already stated the the code will changed to remove the bug and crunchers will eventually be forced to upgrade their BOINc client to run the app_config set up. I've been playing with it and so far I've found that you may be able to drop an app_config file into any of the project folders and assign cores to run them. I have an i7-860 that is currently running 4 cores on WCG ( 3 on SN2S and 1 on CEP2) and 2 cores on Skynet POGS. Later today I'm going to see if I can get the other 2 cores to run Docking or Lattice or maybe one of each .



    You'll never know what you're living for until you know what you're willing to die for.

  3. #3
    Platinum Member
    Mumps's Avatar
    Join Date
    October 28th, 2010
    Location
    Milwaukee, WI
    Posts
    3,994

    Re: Help Conquer Cancer app_info.xml files

    Quote Originally Posted by nanoprobe View Post
    There was also a bug found in the WCG server code that was allowing the app_info platform to work. The techs have already stated the the code will changed to remove the bug and crunchers will eventually be forced to upgrade their BOINc client to run the app_config set up. I've been playing with it and so far I've found that you may be able to drop an app_config file into any of the project folders and assign cores to run them. I have an i7-860 that is currently running 4 cores on WCG ( 3 on SN2S and 1 on CEP2) and 2 cores on Skynet POGS. Later today I'm going to see if I can get the other 2 cores to run Docking or Lattice or maybe one of each .
    Now that sounds superbly interesting! You mean DA finally gave us a way to circumvent DA's braindead scheduling? So, if I have 8 projects all at equal Resource Share on an 8 Core box, I can force it to only run one task per project so I can get the desired distribution of effort. Rather than having one naughty project over-cache and suck away all the resources as the client determines that's the only way it can make deadline. Leaving the other seven starved of their fair share.

  4. #4
    Silver Member
    nanoprobe's Avatar
    Join Date
    August 27th, 2012
    Location
    Classified
    Posts
    810

    Re: Help Conquer Cancer app_info.xml files

    Quote Originally Posted by Mumps View Post
    Now that sounds superbly interesting! You mean DA finally gave us a way to circumvent DA's braindead scheduling? So, if I have 8 projects all at equal Resource Share on an 8 Core box, I can force it to only run one task per project so I can get the desired distribution of effort. Rather than having one naughty project over-cache and suck away all the resources as the client determines that's the only way it can make deadline. Leaving the other seven starved of their fair share.
    It's working, sorta. Instead of Docking or Lattice I'm now using the other 2 cores to run SIMAP. I only have the cache set for 2 days and it doesn't load an equal amount of tasks so each project will get 2 days of work, it just totals them all up for the 2 days. I use Boinctasks so I just suspended the tasks that were in cache that already had 2 days worth and let the other projects fill up with 2 days worth 1 at a time. I don't know what setting the overall cache higher would do but I doubt it would spread out the load among the projects evenly. Even so you could set a higher cache and with a little micro-management fill up each project and forget it for however many days of cache you desire. Not perfect but it's not that hard to manage.(so far )
    Now I don't have each project with an equal resource share so that's something else I'll have to play with.
    Now that it's possible to assign a specific project to x amount of cores maybe there is a way DA can make it so each project gets the amount of tasks per cache setting. Where's the suggestion box?



    You'll never know what you're living for until you know what you're willing to die for.

  5. #5
    Silver Member

    Join Date
    November 11th, 2011
    Posts
    205

    Re: Help Conquer Cancer app_info.xml files

    Quote Originally Posted by Mumps View Post
    Now that sounds superbly interesting! You mean DA finally gave us a way to circumvent DA's braindead scheduling? So, if I have 8 projects all at equal Resource Share on an 8 Core box, I can force it to only run one task per project so I can get the desired distribution of effort. Rather than having one naughty project over-cache and suck away all the resources as the client determines that's the only way it can make deadline. Leaving the other seven starved of their fair share.
    While it's possible to force the client to only run 1 task per application, where's nothing stopping the client from downloading a full cache for this application, meaning your 8-core box has 7 idle cores...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •