|
1)
Message boards :
News :
ATM
(Message 60398)
Posted 9 May 2023 by kksplace Post: When I attempt to Abort two of these WUs, nothing seems to happen at all. Both tasks still show "Uploading" and the Transfers page still shows them at 0%. I have tried "Retry Now" on the Transfers page several times (each) to no avail. Should I instead "Abort Transfer"? |
|
2)
Message boards :
News :
ATM
(Message 60209)
Posted 27 Mar 2023 by kksplace Post: The problem is not the time they take to run. I agree with this. I had one error out on a restart two days ago after reaching nearly 100% due to no checkpoints. Not only that, but it then only showed 37 seconds of CPU time, so it doesn’t show what really happened. My latest one did complete but showed no check points. Therefore the long run time of is more of a high risk for a potential interruption. |
|
3)
Message boards :
News :
ATM
(Message 60043)
Posted 8 Mar 2023 by kksplace Post: Thanks for the idea. Sure enough, that file is showing activity (On sample 324, replica 3 for me.) OK. Just going to sit and wait. Ian&Steve, thanks for the explanation. Just one thought: what if the fourth item is just "do everything else"? Couldn't that mean going straight from 75% to 100% at some point (assuming it is progressing)? |
|
4)
Message boards :
News :
ATM
(Message 60039)
Posted 8 Mar 2023 by kksplace Post: Is there a way to tell if an ATM WU is progressing? I have had only one succeed so far over the last several weeks. However, all of the failures so far were one of two types: either a failure to upload (and the download aborted by me) or a simple "Error while computing", which happened very quickly. However, I now have an ATM WU which has been processing for over seven hours. Looking at the WU properties, it shows the CPU time nearly equal to the elapsed time. The GPU shows processing spikes up to 99%, and the 'down' periods are short. As others have reported, the Progress shows 75% steadily. I am inclined to keep letting it compute, but want to know what behavior others have seen on successful ATM WUs. |
|
5)
Message boards :
Number crunching :
ATM: Free Energy Calculations new application
(Message 59991)
Posted 26 Feb 2023 by kksplace Post: I just aborted the upload (not the workunit) and then it was reported as valid. Partially successful for me. I attempted with two of these and one ended up as "Upload failed" while the other "Completed and validated". |
|
6)
Message boards :
News :
Experimental Python tasks (beta) - task description
(Message 59393)
Posted 3 Oct 2022 by kksplace Post: I am limited on any technical knowledge and can only speak how I got mine to work with 2 tasks. Sorry I can't help anymore. As to getting 3 tasks, my understanding from other posts and my own attempt is that you can't without a custom client or some other behind-the-scenes work. The '2 tasks at one time' limit is a GPUGrid restriction somewhere. |
|
7)
Message boards :
News :
Experimental Python tasks (beta) - task description
(Message 59389)
Posted 2 Oct 2022 by kksplace Post: Let me offer another possible "solution". (I am running two Python tasks on my system.) I found I had to change my Resource Share much, much higher for GPUGrid to effectively share other projects. I originally had Resource shares of 160 for GPUGrid vs 10 for Einstein and 40 for TN-Grid. Since the Python tasks 'use' so much CPU time in particular (at least reported CPU time), it seems to affect the Resource Share calculations at well. I had to move my Resource Share of GPUGrid (for example) to 2,000 to get it both to do two at once and to get Boinc to share with Einstein and TN-Grid roughly the way I wanted. (Nothing magic about my Resource Share ratios; just providing an example of how extreme I went to get it to balance the way I wanted.) Regarding the estimated time to completion, I have not seem them correct on my system yet, though it is getting better. At first Python tasks were starting at 1338 days (!) and now are at 23 days to start. Interesting to hear some of yours are showing correct! What setup are you using in the hosts showing correct times? |
|
8)
Message boards :
Number crunching :
Changing GPU driver
(Message 59318)
Posted 25 Sep 2022 by kksplace Post: Thank you. I had seen the Python tasks act as you say, but wasn't sure if they would survive a driver change. |
|
9)
Message boards :
Number crunching :
Changing GPU driver
(Message 59316)
Posted 25 Sep 2022 by kksplace Post: I am wanting to change my driver from the 510 series to the 515 series. For the ACEMD tasks, if you paused a task and changed drivers it would fail after the reboot. Is that also true for the Python tasks? Should I finish the current tasks before changing the video driver? |
|
10)
Message boards :
Number crunching :
Python apps for GPU hosts 4.03 (cuda1131) using a LOT of CPU
(Message 59282)
Posted 20 Sep 2022 by kksplace Post: As another reference, I have an i7-7820x (8 core, 16 thread) overclocked to 4.4 with an EVGA 3080 (memory clock set to +500, no other overclock) running 2x of these WUs. The GPU is loaded between 50 and 85% (rare dips down to 35%). (Linux Mint OS). |
|
11)
Message boards :
News :
Experimental Python tasks (beta) - task description
(Message 58539)
Posted 20 Mar 2022 by kksplace Post: Well, after a suspend and allowing it to run, it went back to its checkpoint and has shown no progress since. I will abort it. Keep on learning.... |
|
12)
Message boards :
News :
Experimental Python tasks (beta) - task description
(Message 58537)
Posted 20 Mar 2022 by kksplace Post: This task https://www.gpugrid.net/result.php?resultid=32841161 has been running for nearly 26 hours now. It is the first Python beta task I have received that appears to be working. Green-With-Envy shows intermittent low activity on my 1080 GPU and BoincTasks shows 100% CPU usage. It checkpointed only once several minutes after it started and has shown 50% complete ever since. Should I let this task continue or abort it? (Linux Mint, 1080 driver is 510.47.03) |
|
13)
Message boards :
Number crunching :
Making Python GPU tasks to succeed - User side
(Message 58314)
Posted 24 Jan 2022 by kksplace Post: First of all, thank you for consolidating this information. It is very helpful to have this all in one place instead of following through several threads and piecing it together. Next, just for my case, I did not have to do all the steps you have to get my host to work. I am working from Linux Mint that I keep up to date/latest version. All worked on my system from the start for these WUs. Just another data point... And I agree with the 16 GB RAM requirement. It might also be useful to note here that these WUs also use multiple CPU cores/threads. As noted on the other discussion, they seem to use whatever is available. |
|
14)
Message boards :
News :
Experimental Python tasks (beta) - task description
(Message 58148)
Posted 17 Dec 2021 by kksplace Post: I got the first one of the Python WUs for me, and am a little concerned. After 3.25 hours it is only 10% complete. GPU usage seems to be about what you all are saying, and same with CPU. However, I also only have 8 cores/16 threads, with 6 other CPU work units running (TN Grid and Rosetta 4.2). Should I be limiting the other work to let these run? (16 GB RAM). |
|
15)
Message boards :
Number crunching :
some hosts won't get tasks
(Message 57583)
Posted 11 Oct 2021 by kksplace Post: After not crunching for several months I started back again about a month ago. It took some time due to limited work units, but I received some GPUGrid WUs starting the first week of October, but now haven't received any since October 6th. I have tried snagging one when some are showing as available and only receive a message "No tasks are available for New version of ACEMD" on BOINC Manager Event log. Any ideas what I may have changed/not set correctly? (I am receiving and crunching Einstein and Milkway WUs. GPUGrid resource share is set 15 times higher than Einstein and 50 times higher than Milkyway.) Nvidia 1080 Driver 470.63.01 Cuda Version: 11.4 Linux Mint OS Edit: I have also tried a project reset, which did not help. Computer is not hidden. Thank you for taking a look. |
|
16)
Message boards :
News :
New D3RBanditTest workunits
(Message 56644)
Posted 20 Feb 2021 by kksplace Post: Thank you! It worked. Odd, since it was working on Einstein. Just for my ongoing learning, where did you see that no driver was being reported to GPUGRID? Again, thank you for your help. |
|
17)
Message boards :
News :
New D3RBanditTest workunits
(Message 56642)
Posted 20 Feb 2021 by kksplace Post: Seeking some help if possible. I have had only one of the new work units download to my computer on 15 Feb. Unfortunately, it was interrupted by a power loss in my area, and when power came back on I discovered the Nvidia driver had somehow been corrupted. After the fix, the WU ended up with a compute error. The problem is that since then I have not received any more WUs, either automatically or during mulitple Updates in BOINC. Can someone look at my computer and see what I may have set wrong (driver etc) that may be preventing me getting work units? I have checked what my limited knowledge allows. Thank you for any help. EDIT: Computer with the Nvidia 1080. |
|
18)
Message boards :
Number crunching :
Anaconda Python 3 Environment v4.01 failures
(Message 55983)
Posted 11 Dec 2020 by kksplace Post: Not a technical guru like you all here, but if it helps, my system has had one Anaconda failure back on 4 Dec, and now completed 4 in the last several days with one more in progress. Let me know if I can provide any information that helps. |
|
19)
Message boards :
News :
More Acemd3 tests
(Message 52598)
Posted 7 Sep 2019 by kksplace Post: This test WU was suspended twice (once using Suspend, once using Suspend GPU in BOINC Manager) and successfully restarted and completed. http://www.gpugrid.net/result.php?resultid=21354832 |
|
20)
Message boards :
Number crunching :
Too many errors!!
(Message 52327)
Posted 23 Jul 2019 by kksplace Post: The GPU 0 in your PC is quite hot (85°C=185°F), that may cause workunits to freeze. My personal experience is that this temperature doesn't cause problems. I have been crunching GPUGrid for over a year now (24/7) with a 1070 in a case with airflow problems that crunches GPUGrid WUs at between 82 and 85 degrees. Feel free to check my recent tasks to confirm. I might be decreasing the life of the GPU (time will tell), but at least in my case everything is working OK. (I am now looking at cooling options for this one. Because of my experience from my first build (Linux only), I have gained some confidence in trying modifications for the Dell machine with the 1070.) |
©2026 Universitat Pompeu Fabra