 |
|
|
1)
Message boards :
Number crunching :
Abort tasks on dead computer
(Message 63062)
Posted 1 Dec 2020 by Fardringle Post: I thought that might be the case. Thanks for the answer! |
|
2)
Message boards :
Number crunching :
Abort tasks on dead computer
(Message 63027)
Posted 26 Nov 2020 by Fardringle Post: One of my computers is permanently deceased, and therefore will not ever complete the tasks that are assigned to it. In most projects, tasks will be marked as "abandoned" if they are not completed before the deadline. But since these tasks won't expire for a full year, they'll just be sitting there waiting for trickles that will never come. Is there a way to manually cancel them so they can be reassigned to someone else who will be able to complete them properly? This is the computer in question: https://www.cpdn.org/results.php?hostid=1510304 |
|
3)
Questions and Answers :
Unix/Linux :
Almost all tasks fail in Linux Mint
(Message 62946)
Posted 13 Nov 2020 by Fardringle Post: Running 5 tasks simultaneously is using almost 20GB of RAM in Linux at this point, but they do seem to be running well now and were awarded credits for trickles on Thursday, so I appreciate the help! |
|
4)
Questions and Answers :
Unix/Linux :
Almost all tasks fail in Linux Mint
(Message 62908)
Posted 8 Nov 2020 by Fardringle Post: The RAM is set to dynamic so it increases or decreases depending on the actual RAM usage in the VM. It's set to a minimum of 10GB, but can go up to 24GB if needed. That does tend to make the BOINC client stats look a little odd, though. Also, the client that you linked to is a second virtual machine that I turned off completely because all of the CPDN tasks running on it had failed with errors. The only one running right now is named 3900X-Linux-VM1 and as of this moment it is using 12GB RAM with 5 climateprediction tasks actively running. |
|
5)
Questions and Answers :
Unix/Linux :
Almost all tasks fail in Linux Mint
(Message 62904)
Posted 8 Nov 2020 by Fardringle Post: These models are big. They take up about 1.4 GB of memory per task. They are also L3 cache hogs, optimally liking 3-4 MB per task. You don't need that much L3 per task, but having a lot less really slows things down. You may be trying to run too many at a time. Try to suspend all but 6 or 8 and see if those will run okay.Thank you for the suggestion. I've never had more than about 6 running at any one time, but I'll try suspending a few to see if it makes a difference. Edit...Also, even those tasks that ran awhile before crashing, didn't make it to the first trickle. These trickle once per model month and even the fastest PCs running very few models trickle in less than 1.5 days of CPU time.I did notice the lack of trickles but wasn't sure if that was a difference in the Linux app or not, as the few tasks I have running on a Windows machine have been sending in trickles quite frequently. Is it possible that the Climate Prediction app just doesn't run well in a virtual machine? Or maybe not in Linux Mint? I haven't had any trouble running other BOINC projects in this Linux VM... |
|
6)
Questions and Answers :
Unix/Linux :
Almost all tasks fail in Linux Mint
(Message 62902)
Posted 8 Nov 2020 by Fardringle Post: I don't know how to tell if this is a problem with my computer, or with the tasks, or with BOINC, or something else, so I'm hoping one of you will know so that I don't waste more time on it and/or cause problems with the project results. This computer is running Linux Mint 20 in a Hyper-V VM (host is Windows 10). It is allowed to use all 24 cores of the Ryzen 9 3900X CPU if it wants to, is allowed to have up to 24GB of the host's 32GB of RAM, and has 128GB of disk space (about 60GB actually used, most of it in the BOINC folders). There aren't any other projects running on this computer at this time except for WUProp. I actually had a few other VMs that I set up when I saw that some CPDN tasks were showing up, in hope that the other VMs would grab a few as well, but they all failed almost immediately so I shut them down and am only running this one for now. Most of the tasks that I got on November 1 failed after running for only a few minutes so I figured it was just a problem with the specific batch. But several others have failed after running for multiple days. Three more of the first set of tasks are still running and appear to be making progress, although their elapsed time doesn't seem to be matching the actual time they have been running (showing about 5 days elapsed time after running for 7+ days). They also don't seem to be doing any trickles, although again I'm not sure exactly how to tell if that's the case. This computer just got another batch of 8 new tasks today so I'd like to try to figure out what is going wrong before these fail as well... https://www.cpdn.org/results.php?hostid=1510139 |
©2024 climateprediction.net