Results 1 to 3 of 3

Thread: App_Config Files Don't Play Nicely with Backup Projects

  1. #1
    Platinum Member
    Maxwell's Avatar
    Join Date
    October 25th, 2010
    Location
    Everett, WA
    Posts
    3,273

    App_Config Files Don't Play Nicely with Backup Projects

    If this is common knowledge, pardon me; but I just discovered this fact this morning, so I figured I'd share.

    If you're using an app_config file to limit the number of WUs that are crunched simultaneously on a project, and your other projects run out of work, you will NOT receive WUs from your backup project.

    As an example, I'm running 1 Atlas WU/computer. I'm also trying to crunch Rioja and IGEM for goals. However, both of those projects ran out of work, leaving my machines dry. I had set up NFS as a backup, but that did not kick in, since I had enough Atlas WUs downloaded to cover all my threads. [NFS has been a great backup on machines where I've not been running Atlas.]

  2. #2
    Diamond Member
    zombie67's Avatar
    Join Date
    October 24th, 2010
    Location
    Dublin, CA
    Posts
    5,761

    Re: App_Config Files Don't Play Nicely with Backup Projects

    Yes, BOINC work fetch is not smart enough to understand that all tasks downloaded cannot run on all threads.
    A state where police work is easy, is also known as a police state.


    Avatar source
    Twitter: @zombie_67



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

    Re: App_Config Files Don't Play Nicely with Backup Projects

    If only it'd be smart enough to rely on the nidle count for requesting work from the backup projects rather than what's in cache.

Posting Permissions

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