Message boards : Questions and problems : Please, help - too many downloaded jobs/too many jobs in progress
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Send message Joined: 29 Aug 05 Posts: 15542 |
In that case I can forego all other options and point out <exclude_gpu> in cc_config.xml: https://boinc.berkeley.edu/wiki/Client_configuration#Options <exclude_gpu>With the above option you can exclude the weaker GPU per project, if you have more than one. You write one such section per project in cc_config.xml E.g. <cc_config> <log_flags> </log_flags> <options> <exclude_gpu> <url>http://einstein.phys.uwm.edu/</url> <device_num>0</device_num> <type>NVIDIA</type> </exclude_gpu> </options> </cc_config>This will exclude Nvidia GPU 0 from being used at Einstein@Home. The type is used if you have more than one device 0 in your list. When you have an AMD, Intel and Nvidia GPU, they're all device 0, as the numbering is per GPU class. |
Send message Joined: 8 Nov 19 Posts: 718 |
The simplest method would be to either disable network access in the manager, the option is there; disconnect the wifi or Ethernet of your PC (either in software, or unplug the hardware), or install netlimiter. There used to be a free version of netlimiter that allowed you to set up a schedule for enabling/disabling certain programs to access the wifi. It's a windows program. I'm sure there are other programs out there that can do the same. As soon as the network is back online, the PC will upload all processed data, and download more. Setting it to pre-fetch at least 1 day of tasks, allows your PC to crunch constantly. |
Send message Joined: 11 May 20 Posts: 13 |
Hi Jord, thanks very much for the excellent answer, it is greatly appreciated and very useful for me and works:D If you do not mind, I would like to ask one more question, but I promise the last one:) I have a computer which has got 8 cores, but only 6GB RAM and I cannot upgrade it. Unfortunately, it is not enough for Rosetta, so usually 4-5 cores work and the rest wait. I would like to run some less memory consuming projects to use all cores, but it happens that the second project takes more cores than it should. My questions are: 1. Is there any option to prioritise projects? So, the first project takes as many cores as possible and in a case not all are taken the second project can run their jobs? I tried to play with share ratio, but it does not work as I wanted. 2. How can I fix number of cores to a project, e.g. I would like to have 4 cores for Rosetta (even if sometimes Rosetta can run just 3 process due to RAM limitation), 3 cores for nanoHUB and one core for NumberFields and it does not matter if there are jobs for a project or not, cores assigned firmly to a project. Thanks in advance for your help. |
Send message Joined: 29 Aug 05 Posts: 15542 |
Prioritise, no. But both your questions can be handled with an app_config.xml file in each project's sub-directory in the data directory. See https://boinc.berkeley.edu/wiki/Client_configuration#Project-level_configuration for more on that. I haven't yet used any of these on my system, so will leave it to someone else to hopefully walk by and help you write them. But essentially it'll be something like: <app_config> <app_version> <app_name>rosetta</app_name> <avg_ncpus>4</avg_ncpus> </app_version> <app_version> <app_name>minirosetta</app_name> <avg_ncpus>4</avg_ncpus> </app_version> <project_max_concurrent>4</project_max_concurrent </app_config>for Rosetta. The above has two sections for each distinct Rosetta application, it's normal Rosetta app and the Minirosetta app. You save the app_config.xml file into the BOINC/projects/boinc.bakerlab.org_rosetta/ directory. I don't know the application names for the other projects. And also don't quite sure the above works (though it should). What you can also do with Rosetta is turn the Target CPU run time of the tasks down via its project preferences. Default they're set to 8 hours and those can take up to 1.3GB per task. Set to lower times will also lower the memory usage. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.